public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: problem in booting HP zx6000 with stock kernel 2.5.75
Date: Thu, 13 Nov 2003 17:41:41 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106874596811058@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106840426422921@msgid-missing>

On Thu, Nov 13, 2003 at 02:51:43PM +0000, Matthew Wilcox wrote:
> Jesse and I discussed this yesterday.  To take advantage of the
> new multiple-defconfigs scheme in 2.6, what we need to do is:
> 
>  - Create files called arch/ia64/configs/*_defconfig
>  - To use them, type "make zx1_defconfig" (for example).
>  - Keep them up to date ...
> 
> There's a bikeshed question about which configs to support.  I think
> the rule is pretty simple -- if someone's willing to step up and maintain
> the config for a platform, let's put it in.
> 
> I'd suggest we want to have defconfig as generic, then add configs/
> 
>  - zx1_defconfig
>  - sn2_defconfig
>  - dig_defconfig (should work for bigsur, lion, tiger boxes)
>  - sim_defconfig
> 
> I don't mind maintaining the zx1_defconfig if nobody else wants to.

Sounds like a plan to me.  I'll take care of sn2_defconfig.  Seems like
these files should go in shortly after 2.6.0 releases so that people
have something usable for the stable kernel.

Jesse

  parent reply	other threads:[~2003-11-13 17:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 18:57 problem in booting HP zx6000 with stock kernel 2.5.75 David Mosberger-Tang
2003-11-10  5:14 ` Ameya Mitragotri
2003-11-10  5:40 ` Deepak Kumar Gupta, Noida
2003-11-10 16:16 ` Alex Williamson
2003-11-12  5:46 ` Ian Wienand
2003-11-12 16:51 ` Jesse Barnes
2003-11-13 14:51 ` Matthew Wilcox
2003-11-13 17:41 ` Jesse Barnes [this message]
2003-11-13 22:45 ` Peter Chubb
2003-11-14 13:11 ` Matthew Wilcox
2003-11-18  6:39 ` problem in booting HP zx6000 with stock kernel 2.4.18 Deepak Kumar Gupta, Noida
2003-11-18 12:59 ` Matthew Wilcox

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=marc-linux-ia64-106874596811058@msgid-missing \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@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