From: Randy Dunlap <randy.dunlap@oracle.com>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
trapdoor6@gmail.com, Michal Marek <mmarek@suse.cz>,
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 10:58:19 -0800 [thread overview]
Message-ID: <4CFD324B.8050800@oracle.com> (raw)
In-Reply-To: <AANLkTi=uMk74hYa-2aoVgj-F1h=+zGC2T=m4i__OwwQM@mail.gmail.com>
On 12/06/10 10:56, Arnaud Lacombe wrote:
> Hi,
>
> On Mon, Dec 6, 2010 at 1:03 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> On 12/06/10 10:01, Catalin Marinas wrote:
>> [...]
>>> This could be simplified to only show the first option of every '&&'
>>> expression, something like below:
>>>
>>> warning: I2C_ISCH selects MFD_CORE...
>>> warning: GPIO_SCH selects MFD_CORE...
>>>
>>> But I couldn't figure out whether the expression reduction code in
>>> kbuild reorders the options or not.
>>
> This was the purpose of a patch I send a month or two ago, though, you
> defeated it with cases the code was not taking into account. I updated
> it since, but did not post it. I'll post it on linux-kbuild@ and
> continue the discussion there.
>
>> I'm pretty sure that I have seen cases where the faulty kconfig is not the
>> first one listed, so all of them need to be available.
>>
> do you have an example ?
Not at hand, but I'll be on the lookout for one.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-12-06 19:01 UTC|newest]
Thread overview: 10+ 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
[not found] ` <AANLkTimeyo==XJWUaUs8EzJvA8azkk3sw9FXQhMjuo6M@mail.gmail.com>
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 [this message]
2010-12-05 16:13 ` Arnaud Lacombe
2010-12-05 16:43 ` trapDoor
2010-12-06 6:44 ` Michal Marek
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=4CFD324B.8050800@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mmarek@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox