linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnaud Lacombe <lacombar@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, mikey@neuling.org,
	linux-kbuild@vger.kernel.org, netdev@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, paulus@samba.org,
	jeffrey.t.kirsher@intel.com, akpm@linux-foundation.org,
	torvalds@linux-foundation.org
Subject: Re: linux-next: boot test failure (net tree)
Date: Mon, 22 Aug 2011 23:50:02 -0400	[thread overview]
Message-ID: <CACqU3MW4BnucRt3gxPrKPDvWEjaVuxRF1VOPWk5hTRfneyANkg@mail.gmail.com> (raw)
In-Reply-To: <20110822.191348.2099822249437201579.davem@davemloft.net>

Hi,

[Added linux-kbuild@ to the Cc: list.]

On Mon, Aug 22, 2011 at 10:13 PM, David Miller <davem@davemloft.net> wrote:
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 23 Aug 2011 11:41:29 +1000
>
>> On Tue, 23 Aug 2011 11:40:11 +1000 Stephen Rothwell <sfr@canb.auug.org.a=
u> wrote:
>>>
>>> On Mon, 22 Aug 2011 11:30:32 +1000 Stephen Rothwell <sfr@canb.auug.org.=
au> wrote:
>>> >
>>> > Here's what I am applying as a merge fixup to the net tree today so t=
hat
>>> > my ppc64_defconfig builds actually build more or less the same set of
>>> > drivers as before this rearrangement.
>>>
>>> And this today:
>>
>> And this:
>
> I'm starting to get uncomfortable with this whole situation, and I
> feel more and more that these new kconfig guards are not tenable.
>
> Changing defconfig files might fix the "automated test boot with
> defconfig" case but it won't fix the case of someone trying to
> automate a build and boot using a different, existing, config file.
> It ought to work too, and I do know people really do this.
>
> And just the fact that we would have to merge all of these defconfig chan=
ges
> through the networking tree is evidence of how it's really not reasonable
> to be doing things this way.
>
> Jeff, I think we need to revert the dependencies back to what they were
> before the drivers/net moves. =A0Could you prepare a patch which does tha=
t?
>
Are you implying we need some kind of way to migrate config ?

 - Arnaud

  parent reply	other threads:[~2011-08-23  3:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110816.171525.639251389938336183.davem@davemloft.net>
     [not found] ` <20110817105002.efebf85d08460ad99b14be8e@canb.auug.org.au>
     [not found]   ` <20110818152214.661858a61496993aaef2c704@canb.auug.org.au>
     [not found]     ` <20110817.225356.1790362313048139752.davem@davemloft.net>
2011-08-22  1:30       ` linux-next: boot test failure (net tree) Stephen Rothwell
2011-08-23  1:40         ` Stephen Rothwell
2011-08-23  1:41           ` Stephen Rothwell
2011-08-23  2:13             ` David Miller
2011-08-23  2:26               ` Jeff Kirsher
2011-08-23  3:50               ` Arnaud Lacombe [this message]
2011-08-23  4:02                 ` David Miller
2011-08-23  8:29                   ` Jeff Kirsher

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=CACqU3MW4BnucRt3gxPrKPDvWEjaVuxRF1VOPWk5hTRfneyANkg@mail.gmail.com \
    --to=lacombar@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).