Re: hwmon.c as a kernel module in 3.18

[Ani Sinha]

Never mind. I figured it out. The commit that changed the behavior is :

commit de0a41484c47d783dd4d442914815076aa2caac2
Author: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
Date:   Mon Oct 1 11:43:49 2012 -0400
    tg3: unconditionally select HWMON support when tg3 is enabled.

So I had exactly this combination : CONFIG_TG3 was 'y' whereas
CONFIG_HWMON was 'm'.

I have fixed it now.

thanks
ani



On Tue, May 24, 2016 at 1:10 PM, Ani Sinha <ani@xxxxxxxxxx> wrote:
> Hi guys :
>
> I am facing this interesting issue and I can't quite figure out what
> the root cause is. Any help will be greatly appreciated.
>
> In my old 3.4 kernel, I had configured HWMON (CONFIG_HWMON) as a
> module ('m'). Now I am trying to upgrade to 3.18 and I am trying to
> keep the same kernel configuration as much as I can. The weird thing
> is, after setting CONFIG_HWMON to 'm. when I do config oldconfig, it's
> setting it back to 'y' (in-built module). I can't figure out which
> kernel option is turning the 'm' to 'y'. I have done menuconfig, then
> searched for the symbol and then looked at all the dependencies.
> However I am still clueless. I am wondering if there is some debug
> option which when turned on will print out some logs which will give
> me more insights into why this is happening.
>
> thanks a lot in advance
> ani