From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756305AbcGZMx7 (ORCPT ); Tue, 26 Jul 2016 08:53:59 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:36453 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753905AbcGZMxz convert rfc822-to-8bit (ORCPT ); Tue, 26 Jul 2016 08:53:55 -0400 MIME-Version: 1.0 In-Reply-To: <20160726061229.3339cfae@lwn.net> References: <20160726074543.21311-1-sunny@sunbase.org> <20160726061229.3339cfae@lwn.net> From: =?UTF-8?B?w5h5dmluZCBBLiBIb2xt?= Date: Tue, 26 Jul 2016 14:53:24 +0200 X-Google-Sender-Auth: lJU-ZSUknXdNMxrp3yedQubxLkQ Message-ID: Subject: Re: [PATCH] README: Mention when 386 support ended + update obsolete 386 paths To: Jonathan Corbet Cc: linux-kernel@vger.kernel.org, Diego Viola , Jiri Kosina , Vineet Gupta Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26 July 2016 at 14:12, Jonathan Corbet wrote: > On Tue, 26 Jul 2016 09:45:43 +0200 Øyvind A. Holm > 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? That was also my first thought, yes. But then I thought, maybe there's some value to that information in case someone wants to try a new kernel on some ancient hardware. But it's probably an unlikely scenario. I'll send a new patch now. Øyvind