public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Christian Kujau <evil@g-house.de>, Tom Rini <trini@kernel.crashing.org>
Cc: Sven Hartge <hartge@ds9.gnuu.de>,
	linux-kernel@vger.kernel.org,
	linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.6.5-pre* does not boot on my PReP PPC
Date: Mon, 5 Apr 2004 16:48:26 -0500	[thread overview]
Message-ID: <200404051648.26220.hollisb@us.ibm.com> (raw)
In-Reply-To: <4071CD50.2000402@g-house.de>

On Monday 05 April 2004 16:19, Christian Kujau wrote:
> um, yes. but the target "common_defconfig" was disabled somewhere in
> 2.5, so my shini script broke. i wanted to do common_defconfig first,
> then always keep my .config and do "oldconfig" after patching, but
> somehow my script broke, so i went with "allnoconfig"...but ok, i'll try
> again.

FWIW, I use ibmchrp_config and then enable a couple PReP-specific things. It's 
pretty bare...

-- 
Hollis Blanchard
IBM Linux Technology Center


  reply	other threads:[~2004-04-05 21:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 18:33 2.6.5-pre* does not boot on my PReP PPC Meelis Roos
2004-03-26 18:51 ` Tom Rini
2004-03-27 13:55   ` Sven Hartge
2004-03-29 15:09     ` Tom Rini
2004-03-29 15:15     ` Tom Rini
2004-03-30 11:31       ` Meelis Roos
2004-03-30 18:45         ` Sven Hartge
2004-04-04 17:34           ` Christian Kujau
2004-04-05 15:50             ` Tom Rini
2004-04-05 21:19               ` Christian Kujau
2004-04-05 21:48                 ` Hollis Blanchard [this message]
2004-04-05 22:30                 ` Hollis Blanchard
2004-04-05 21:45               ` Christian Kujau
2004-04-05 16:15             ` Tom Rini
2004-03-30 18:49       ` Sven Hartge
2004-03-30 19:09         ` Tom Rini
2004-03-26 21:54 ` Christian Kujau
2004-03-27 13:56   ` Sven Hartge

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=200404051648.26220.hollisb@us.ibm.com \
    --to=hollisb@us.ibm.com \
    --cc=evil@g-house.de \
    --cc=hartge@ds9.gnuu.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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