On Mon, 22 Nov 2010 11:48:01 +1100 Stephen Rothwell wrote: > On Fri, 29 Oct 2010 11:37:31 +1100 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > > > > On Tue, 12 Oct 2010 15:19:46 +0200 Michal Marek <mmarek@xxxxxxx> wrote: > > > > > > This reverts commit 71ebc01, which was a 2.6.36-only stopgap solution. > > > > I was hoping that we would have the number of these warnings down to > > something reasonable before this revert made it into Linus' tree ... > > > > I guess fixing the V4L stuff will become a bit more urgent, now :-) > > Is there any chance that the V4L kconfig warnings will be fixed? It is > quite irritating for those of us who do allmodconfig (and allyesconfig) > builds ... Yes, the MEDIA kconfig warnings are irritating. I just use "grep -v MEDIA" to ignore them. :) I haven't seen any email from Michal for more than one week. Hopefully he will be back soon. There are patches from Arnaud Lacombe <lacombar@xxxxxxxxx> to introduce a VISIBLE property for kconfig symbols (this fixes the MEDIA kconfig warnings), but Michal has not commented on them. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
