From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Unable to boot a raw kernel image :??
Date: 5 Mar 2003 16:30:18 -0800 [thread overview]
Message-ID: <b464qq$t0r$1@cesium.transmeta.com> (raw)
In-Reply-To: 1046912881.15971.29.camel@irongate.swansea.linux.org.uk
Followup to: <1046912881.15971.29.camel@irongate.swansea.linux.org.uk>
By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
>
> It seems completely inappropriate to remove a feature from the 'stable'
> kernel tree.
>
Agreed. The only issue is whether or not it's too broken to be
considered a feature at this point (my feeling would be that it's not,
and should be removed in 2.5, not 2.4.)
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
prev parent reply other threads:[~2003-03-06 0:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 13:21 Unable to boot a raw kernel image :?? DervishD
2002-12-03 11:29 ` Denis Vlasenko
2002-12-08 10:33 ` DervishD
2002-12-06 11:45 ` Edgar Toernig
2002-12-08 10:36 ` DervishD
2003-03-05 15:00 ` H. Peter Anvin
2003-03-05 15:33 ` Mikael Pettersson
2003-03-05 15:47 ` H. Peter Anvin
2003-03-05 15:58 ` Mikael Pettersson
2003-03-05 16:02 ` H. Peter Anvin
2003-03-05 16:05 ` Mikael Pettersson
2003-03-06 10:16 ` Mikael Pettersson
2003-03-06 20:28 ` H. Peter Anvin
2003-03-09 10:31 ` DervishD
2003-03-10 19:38 ` H. Peter Anvin
2003-03-11 9:23 ` DervishD
2003-03-05 16:12 ` DervishD
2003-03-05 16:33 ` John Bradford
2003-03-05 16:48 ` H. Peter Anvin
2003-03-05 16:55 ` John Bradford
2003-03-05 17:01 ` DervishD
2003-03-05 18:04 ` John Bradford
2003-03-05 16:51 ` H. Peter Anvin
2003-03-05 17:04 ` DervishD
2003-03-05 17:51 ` H. Peter Anvin
2003-03-06 1:08 ` Alan Cox
2003-03-06 0:30 ` H. Peter Anvin [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='b464qq$t0r$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.