public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: trapdoor6@gmail.com, Michal Marek <mmarek@suse.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	brueckner@linux.vnet.ibm.com, lacombar@gmail.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:03:55 -0800	[thread overview]
Message-ID: <4CFD258B.4030604@oracle.com> (raw)
In-Reply-To: <AANLkTimXRBz7-mz_E_xdc85pGi7ExMy67XfDVF7jEt+Y@mail.gmail.com>

On 12/06/10 10:01, Catalin Marinas wrote:
> On 5 December 2010 16:51, trapDoor <trapdoor6@gmail.com> wrote:
>> On Sun, Dec 5, 2010 at 4:11 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>>> On Sun, 5 Dec 2010 15:42:46 +0000 trapDoor wrote:
>>>
>>>> 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:
>>>>
>>>> warning: (GPIO_RDC321X && PCI && GPIOLIB) selects MFD_RDC321X which
>>>> has unmet direct dependencies (MFD_SUPPORT && PCI)
>>>> warning: (I2C_ISCH && I2C && PCI || GPIO_SCH && GPIOLIB && PCI ||
>>>> GPIO_VX855 && GPIOLIB || GPIO_RDC321X && PCI && GPIOLIB ||
> [...]
>>>> MFD_JZ4740_ADC && MFD_SUPPORT && MACH_JZ4740 || MFD_TPS6586X &&
>>>> MFD_SUPPORT && I2C=y && GPIOLIB && GENERIC_HARDIRQS || MFD_VX855 &&
>>>> MFD_SUPPORT && PCI) selects MFD_CORE which has unmet direct
>>>> dependencies (MFD_SUPPORT)
>>>
>>> That's 2 warnings.  I have sent a patch for the first one.
>>> Looks like I need to resend it.
>>
>> I was actually impressed by the amount of lines produced by those two
>> warnings :) I'd call it 'a lot'.
> 
> 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.

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.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-12-06 18:05 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 [this message]
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

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=4CFD258B.4030604@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