> Which is exactly what my "require SYMBOL2 would give us.This would be a nice feature. In fact, some SELECT's were wrongly added in the past, at V4L/DVB Kconfig's as people understood that this would be the behaviour of SELECT. IMO, I think it is preferred that "SELECT" could act as you've described: Check if all dependencies for the selected symbol are satisfied. If not, auto-selects or prompt to the users. The auto-select feature, without prompting could be very helpful to allow testing kconfig items, since, instead of running all randomconfig's, subsystem maintainers can use scripts that will do something like allnoconfig, and then select just the symbols requested by each driver (*). (*) Something like: make select="DRIVER_FOO" and make select="DRIVER_FOO_MODULE" could just do this: marks NO to everything and Y (or M) to the symbol, and just the required dependencies for that symbol to compile. -- Cheers, Mauro Carvalho Chehab http://linuxtv.org mchehab@infradead.org --
| Linus Torvalds | Linux 2.6.27-rc8 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Linux 2.6.20-rc6 |
| Mike Snitzer | Re: Distributed storage. |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Herbert Xu | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state ch... |
