From: Pavel Machek <pavel@ucw.cz>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Øyvind A. Holm" <sunny@sunbase.org>,
linux-kernel@vger.kernel.org,
"Diego Viola" <diego.viola@gmail.com>,
"Jiri Kosina" <jkosina@suse.com>,
"Vineet Gupta" <Vineet.Gupta1@synopsys.com>
Subject: Re: [PATCH] README: Mention when 386 support ended + update obsolete 386 paths
Date: Fri, 5 Aug 2016 11:22:43 +0200 [thread overview]
Message-ID: <20160805092243.GA19068@amd> (raw)
In-Reply-To: <20160726061229.3339cfae@lwn.net>
On Tue 2016-07-26 06:12:29, Jonathan Corbet wrote:
> On Tue, 26 Jul 2016 09:45:43 +0200
> Øyvind A. Holm <sunny@sunbase.org> wrote:
>
> > - Compiling the kernel with "Processor type" set higher than 386
> > will result in a kernel that does NOT work on a 386. The
> > - kernel will detect this on bootup, and give up.
> > + kernel will detect this on bootup, and give up. The last kernel
> > + with support for 386 was version 3.7.
>
> So we want the documentation to reflect current kernels, not those from
> years gone by. I can't think of a reason why this paragraph should
> continue to exist at all. Can you make a new version that removes it
> altogether?
You may want to generalize it to "will not boot if you se processor
type too high", but I'd keep v3.7 note -- it is going to be tricky to
find out in any other way.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2016-08-05 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 7:45 [PATCH] README: Mention when 386 support ended + update obsolete 386 paths Øyvind A. Holm
2016-07-26 12:12 ` Jonathan Corbet
2016-07-26 12:53 ` Øyvind A. Holm
2016-08-05 9:22 ` Pavel Machek [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=20160805092243.GA19068@amd \
--to=pavel@ucw.cz \
--cc=Vineet.Gupta1@synopsys.com \
--cc=corbet@lwn.net \
--cc=diego.viola@gmail.com \
--cc=jkosina@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sunny@sunbase.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;
as well as URLs for NNTP newsgroup(s).