From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Michal Marek <mmarek@suse•cz>
Cc: randy.dunlap@oracle•com, catalin.marinas@arm•com,
linux-kbuild@vger•kernel.org, linux-next@vger•kernel.org,
linux-kernel@vger•kernel.org, lacombar@gmail•com,
xiyou.wangcong@gmail•com,
Mauro Carvalho Chehab <mchehab@infradead•org>
Subject: Re: [PATCH] Revert "kconfig: Temporarily disable dependency warnings"
Date: Mon, 22 Nov 2010 11:48:01 +1100 [thread overview]
Message-ID: <20101122114801.2eee4c4d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20101029113731.5c7c54b9.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
On Fri, 29 Oct 2010 11:37:31 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> On Tue, 12 Oct 2010 15:19:46 +0200 Michal Marek <mmarek@suse•cz> 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 ...
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-11-22 0:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 0:44 linux-next: build warnings after merge of the kbuild-current tree Stephen Rothwell
2010-10-06 11:13 ` Michal Marek
2010-10-06 11:42 ` Catalin Marinas
2010-10-08 14:51 ` Michal Marek
2010-10-08 15:03 ` Américo Wang
2010-10-08 15:05 ` Michal Marek
2010-10-09 21:45 ` [PATCH] kconfig: Temporarily disable dependency warnings Michal Marek
2010-10-11 15:23 ` Catalin Marinas
2010-10-11 21:46 ` Michal Marek
2010-10-11 21:59 ` Randy Dunlap
2010-10-12 13:19 ` [PATCH] Revert "kconfig: Temporarily disable dependency warnings" Michal Marek
2010-10-29 0:37 ` Stephen Rothwell
2010-11-22 0:48 ` Stephen Rothwell [this message]
2010-11-22 1:44 ` Randy Dunlap
2010-11-22 1:58 ` Arnaud Lacombe
2010-11-22 2:09 ` Randy Dunlap
2010-11-22 2:17 ` Arnaud Lacombe
2010-11-22 2:57 ` Stephen Rothwell
2010-11-22 13:26 ` Mauro Carvalho Chehab
2010-11-25 17:16 ` Arnaud Lacombe
2010-11-25 17:43 ` Catalin Marinas
2010-11-25 18:09 ` Arnaud Lacombe
2010-11-26 12:33 ` Catalin Marinas
2010-11-26 13:33 ` Michal Marek
2010-11-26 14:50 ` Catalin Marinas
2010-11-25 19:26 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101122114801.2eee4c4d.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=catalin.marinas@arm$(echo .)com \
--cc=lacombar@gmail$(echo .)com \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@infradead$(echo .)org \
--cc=mmarek@suse$(echo .)cz \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox