On Sun, Jul 12, 2009 at 10:00 AM, Mikael Pettersson<mikpe@xxxxxxxx> wrote: [...] > I like this concept, but I'd like to see it supported with make oldconfig. 'make oldconfig' uses the same 'scripts/kconfig/conf' program as the 'make config' does, which is supported already in this series of patches, > Let's say I copy a .config from kernel X into kernel Y (Y>X) and make oldconfig. > Sometimes the new kernel will enable some previously disabled option, and > it would be very useful to see WHY. > > To take a concrete example, in my 2.6.30 .config I had: > > CONFIG_DRM=m > CONFIG_DRM_RADEON=m > # CONFIG_FB is not set > > which when oldconfig'd in 2.6.31-rc changed to > > CONFIG_DRM=m > CONFIG_DRM_RADEON=m > CONFIG_FB=m > (+ some more FB stuff) > > In this case it would have been nice to get an explanation that DRM_RADEON > was responsible for (wrongly, IMO) selecting FB. Something like > > # CONFIG_FB was selected by CONFIG_DRM_RADEON > CONFIG_FB=m > > These comments should only be emitted for options added by select that > previously were absent or 'is not set'. The conf system is not so smart to find the recent changes (you may try scripts/diffconfig to diff two .config), Anyway, if you don't like CONFIG_FB and have no idea why it is selected, you can navigate to CONFIG_FB in menuconfig/gconfig/xconfig/config, and find out the real dependency reason from its help message, > > /Mikael > -- Cheng Renquan (程任全), from Shenzhen, China -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
