From: Michal Marek <mmarek@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: trapdoor6@gmail.com,
Linus Torvalds <torvalds@linux-foundation.org>,
brueckner@linux.vnet.ibm.com, mchehab@redhat.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT] kbuild and kconfig fixes for 2.6.37-rc5
Date: Mon, 06 Dec 2010 07:44:16 +0100 [thread overview]
Message-ID: <4CFC8640.2030105@suse.cz> (raw)
In-Reply-To: <AANLkTi=95UvsLTUFkS6bsFk9pO_iGgXfeoMf8BOVm0ed@mail.gmail.com>
On 5.12.2010 17:13, Arnaud Lacombe wrote:
> Hi,
>
> On Sun, Dec 5, 2010 at 10:42 AM, trapDoor <trapdoor6@gmail.com> wrote:
>> On Sat, Dec 4, 2010 at 1:57 PM, Michal Marek <mmarek@suse.cz> wrote:
>>> Hi Linus,
>>>
>>> please pull these kbuild/kconfig fixes for the next -rc. The largest
>>> part are fixes for the annoying kconfig warnings, contributed by Arnaud
>>> Lacombe and Mauro Carvalho Chehab. The solution adds a new 'visible if'
>>> keyword to the Kconfig language, so it's not exactly something that one
>>> would expect in the rc phase, but the kconfig change is not huge (the
>>> large diff is due to generated files) and it is deployed only in those
>>> five Kconfig files that had the warnings and were hard to fix by other
>>> means. The second part is a forgotten patch by Hendrik Brueckner to
>>> usr/initramfs, that fixes build for Blackfin and h8300.
>> Hello,
>> I couldn't wait and I merged the changes into my copy of mainline
>> tree. The merge was successful, no conflicts and the merge-diffstat
>> was exactly the same as above. However, when running oldconfig on the
>> patched kernel I still get lots of warnings:
>>
<sip>
>>
> Technically, this is two warning, though really verbose :)
>
>>
>> Were these warnings supposed to be fixed by this patch set as well? Or
>> is it something in my config (attached)?
>>
> No. The kconfig language update is meant to be a solution for the +150
> warnings triggered by the media and i2c tree, without making it
> impossible to maintain. The notion of "dependency" was too strong for
> the expected usage.
Yes, sorry for giving false hopes in my mail :-).
Michal
prev parent reply other threads:[~2010-12-06 6:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 13:57 [GIT] kbuild and kconfig fixes for 2.6.37-rc5 Michal Marek
2010-12-05 15:42 ` trapDoor
2010-12-05 16:11 ` Randy Dunlap
2010-12-05 16:51 ` trapDoor
2010-12-06 18:01 ` Catalin Marinas
2010-12-06 18:03 ` Randy Dunlap
2010-12-06 18:56 ` Arnaud Lacombe
2010-12-06 18:58 ` Randy Dunlap
2010-12-05 16:13 ` Arnaud Lacombe
2010-12-05 16:43 ` trapDoor
2010-12-06 6:44 ` Michal Marek [this message]
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=4CFC8640.2030105@suse.cz \
--to=mmarek@suse.cz \
--cc=brueckner@linux.vnet.ibm.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=trapdoor6@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.