netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Rick Lindsley <ricklind@us.ibm.com>
Cc: niv@us.ibm.com, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Fw: Re: 2.6.9-rc1-mm2
Date: Wed, 1 Sep 2004 01:41:18 -0700	[thread overview]
Message-ID: <20040901014118.45204bcb.akpm@osdl.org> (raw)
In-Reply-To: <200409010833.i818XPZ04210@owlet.beaverton.ibm.com>

Rick Lindsley <ricklind@us.ibm.com> wrote:
>
> But considering I ran make oldconfig on this and chose
>  the defaults in each and every case, should I end up with a config that
>  doesn't compile?

No, you shouldn't.  This indicates a Kconfig bug.

      reply	other threads:[~2004-09-01  8:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 22:34 Fw: Re: 2.6.9-rc1-mm2 Andrew Morton
2004-09-01  0:49 ` Nivedita Singhvi
2004-09-01  8:33   ` Rick Lindsley
2004-09-01  8:41     ` Andrew Morton [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=20040901014118.45204bcb.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=niv@us.ibm.com \
    --cc=ricklind@us.ibm.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;
as well as URLs for NNTP newsgroup(s).