Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759815Ab2HXRF6 (ORCPT ); Fri, 24 Aug 2012 13:05:58 -0400 Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]:55011 "EHLO mail-lpp01m010-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758491Ab2HXRFz (ORCPT ); Fri, 24 Aug 2012 13:05:55 -0400 MIME-Version: 1.0 In-Reply-To: <201208241854.45656.tweek@tweek.dk> References: <201208241814.16862.tweek@tweek.dk> <5037AAB0.6040102@genband.com> <201208241854.45656.tweek@tweek.dk> Date: Fri, 24 Aug 2012 19:05:53 +0200 Message-ID: Subject: Re: Drop support for x86-32 From: wbrana To: Martin Nybo Andersen Cc: Chris Friesen , Bernd Petrovitsch , Ondrej Zary , linux-kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 744 Lines: 14 On 8/24/12, Martin Nybo Andersen wrote: > What I'd hate even more is rendering my old working hardware useless by > removing x86-32 support from the kernel. To reason the removal by saying > "Microsoft plans to do it" just makes me go bonkers... Your old hardware will work fine with long term kernel. > These legacy apps will most likely be compiled for x86-32 and not x32 (an > argument for not removing x86-32 support on a running x86-64 kernel). Which legacy apps do you mean? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/