public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Ashok Raj <ashok.raj@intel.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, discuss@x86_64.org
Subject: Re: Extending defconfig for x86_64
Date: 22 Jul 2005 18:53:16 +0200
Date: Fri, 22 Jul 2005 18:53:16 +0200	[thread overview]
Message-ID: <20050722165316.GA19123@muc.de> (raw)
In-Reply-To: <20050721124739.A11717@unix-os.sc.intel.com>

On Thu, Jul 21, 2005 at 12:47:39PM -0700, Ashok Raj wrote:
> Hi Andi
> 
> This patch is a trivial one. Provide a differnet defconfig for x86_64. 
> 
> Each time people get bitten by which scsi controller/eth to use. It might
> be possible to setup configs for other systems as well, if there are well
> known system names to make it simple for devl.

The defconfig should be pretty complete. I don't want to add
more to the standard kernel right now sorry because if we start
with that it would never end. But you can always
store them outside the kernel tree.


-Andi

      reply	other threads:[~2005-07-22 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 19:47 Extending defconfig for x86_64 Ashok Raj
2005-07-22 16:53 ` Andi Kleen [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=20050722165316.GA19123@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.com \
    --cc=discuss@x86_64.org \
    --cc=linux-kernel@vger.kernel.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