From: Michal Marek <mmarek@suse.cz>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kbuild@vger.kernel.org, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
lacombar@gmail.com, xiyou.wangcong@gmail.com
Subject: Re: [PATCH] kconfig: Temporarily disable dependency warnings
Date: Mon, 11 Oct 2010 23:46:48 +0200 [thread overview]
Message-ID: <4CB385C8.7010109@suse.cz> (raw)
In-Reply-To: <1286810580.19739.108.camel@e102109-lin.cambridge.arm.com>
On 11.10.2010 17:23, Catalin Marinas wrote:
> On Sat, 2010-10-09 at 22:45 +0100, Michal Marek wrote:
>> After fixing a use-after-free bug in kconfig, a 'make defconfig' or
>> 'make allmodconfig' fills the screen with warnings that were not
>> detected before. Given that we are close to the release now, disable the
>> warnings temporarily and deal with them after 2.6.36.
>>
>> Signed-off-by: Michal Marek <mmarek@suse.cz>
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Thanks, but I already pushed it on Saturday. The good news is that Linus
did pull from me, so 2.6.36 will have this.
Michal
next prev parent reply other threads:[~2010-10-11 21:47 UTC|newest]
Thread overview: 32+ 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 [this message]
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
2010-11-22 1:44 ` Randy Dunlap
2010-11-22 1:58 ` Arnaud Lacombe
2010-11-22 1:58 ` Arnaud Lacombe
2010-11-22 2:09 ` Randy Dunlap
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:16 ` Arnaud Lacombe
2010-11-25 17:43 ` Catalin Marinas
2010-11-25 17:43 ` Catalin Marinas
2010-11-25 18:09 ` Arnaud Lacombe
2010-11-25 18:09 ` Arnaud Lacombe
2010-11-26 12:33 ` Catalin Marinas
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=4CB385C8.7010109@suse.cz \
--to=mmarek@suse.cz \
--cc=catalin.marinas@arm.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.