From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754609AbcGZMMd (ORCPT ); Tue, 26 Jul 2016 08:12:33 -0400 Received: from tex.lwn.net ([70.33.254.29]:42094 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752723AbcGZMMb (ORCPT ); Tue, 26 Jul 2016 08:12:31 -0400 Date: Tue, 26 Jul 2016 06:12:29 -0600 From: Jonathan Corbet To: "=?UTF-8?B?w5h5dmluZA==?= A. Holm" Cc: linux-kernel@vger.kernel.org, Diego Viola , Jiri Kosina , Vineet Gupta Subject: Re: [PATCH] README: Mention when 386 support ended + update obsolete 386 paths Message-ID: <20160726061229.3339cfae@lwn.net> In-Reply-To: <20160726074543.21311-1-sunny@sunbase.org> References: <20160726074543.21311-1-sunny@sunbase.org> Organization: LWN.net X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-redhat-linux-gnu) MIME-Version: 1.0 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 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? Thanks, jon