Re: REGRESSION: Re: [GIT] kconfig rc fixes

[Mauro Carvalho Chehab]

Em 03-11-2010 18:47, Michal Marek escreveu:
> On 3.11.2010 23:29, Mauro Carvalho Chehab wrote:
>> Em 09-10-2010 18:40, Michal Marek escreveu:
>>> The following changes since commit cb655d0f3d57c23db51b981648e452988c0223f9:
>>>
>>>   Linux 2.6.36-rc7 (2010-10-06 13:39:52 -0700)
>>>
>>> are available in the git repository at:
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild-2.6.git rc-fixes
>>>
>>> Arnaud Lacombe (1):
>>>       kconfig: delay symbol direct dependency initialization
>>
>> This patch generated a regression with V4L build. After applying it, some Kconfig
>> dependencies that used to work with V4L Kconfig broke.
> 
> You mean, the dependencies trigger a warning now, right? Also, you are
> replying to my pull request for 2.6.36-rc8, but that pull request also
> included "kconfig: Temporarily disable dependency warnings", so 2.6.36
> final is NOT affected by this, just to clarify. 2.6.37-rc1 reverted this
> workaround and I hope we come to some solution now. BTW,
> http://www.kerneltrap.com/mailarchive/linux-kernel/2010/10/7/4629122/thread
> is how a very similar issue was fixed in the i2c Kconfig (commit 0a57274
> in 2.6.37-rc1 now).

Well, I'm seeing those warnings on 2.6.37-rc1, after the patch that re-enable
the warnings. Just reverting the delay symbol direct dependency init changeset 
makes the warnings stop.

I didn't really try to run lots of tests to be sure that they actually break
anything, or if they are just unwanted warnings, but, in any case, we need a
fix before the end of .37 cycle.

A solution like what was done on i2c doesn't seem nice, as it will require lots
of artificial changes at kconfig stuff. Maybe it would be better to just add
some logic at Kconfig file to specify those kind of menus without producing
warnings, of course assuming that actually won't break symbols dependency solve.

Thanks,
Mauro
anything.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/