From: Cruz Julian Bishop <cruzjbishop@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: wbrana <wbrana@gmail.com>, Chen <hi3766691@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Drop support for x86-32
Date: Sat, 25 Aug 2012 10:57:10 +1000 [thread overview]
Message-ID: <503822E6.5040500@gmail.com> (raw)
In-Reply-To: <20120824173626.0194625c@pyramind.ukuu.org.uk>
On 25/08/12 02:36, Alan Cox wrote:
>> almost all x86-32 boxes will be trash in 2017, remaining boxes will
>> use long term tree
> People will still be manufacturing 32bit x86 processors in 2017 I'm quite
> sure. You appear entirely out of touch. There are already serious
> discussions going on about things like the kernel modifications needed to
> make 32bit systems run past 2038.
>
> Besides which what Linux supports is defined by what peope chose to
> contribute code for. We support 32bit 680x0 machines that have been
> obsolete for nigh on 20 years because someone chooses to support them.
>
> For that matter if someone comes along with DEC-10 port and it works as
> was clean without messing up the core I'm sure we'd add that too!
Is that a hint? :P
> Alan
>
>
> --
> 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/
next prev parent reply other threads:[~2012-08-25 0:57 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 10:41 Drop support for x86-32 wbrana
[not found] ` <201208231814.21168.tweek@tweek.dk>
2012-08-23 17:22 ` wbrana
2012-08-23 17:51 ` Ondrej Zary
2012-08-23 18:07 ` wbrana
2012-08-24 12:40 ` Bernd Petrovitsch
2012-08-24 12:59 ` wbrana
2012-08-24 13:51 ` wbrana
2012-08-24 15:48 ` Bernd Petrovitsch
2012-08-24 15:55 ` wbrana
[not found] ` <CANQmPXj6VsxP596xeU5SZaL=eyDJR4_ShBxCJVqthYTdNA4HSw@mail.gmail.com>
2012-08-24 16:11 ` wbrana
2012-08-24 16:14 ` Martin Nybo Andersen
2012-08-24 16:17 ` wbrana
2012-08-24 16:20 ` Bobby Powers
2012-08-24 16:24 ` wbrana
2012-08-24 16:20 ` Martin Nybo Andersen
2012-08-24 16:26 ` wbrana
[not found] ` <201208241832.09577.tweek@tweek.dk>
2012-08-24 16:39 ` wbrana
2012-08-24 16:24 ` Chris Friesen
2012-08-24 16:54 ` Martin Nybo Andersen
2012-08-24 17:05 ` wbrana
2012-08-24 17:25 ` Chris Friesen
2012-08-24 17:28 ` Brian Gerst
2012-08-24 18:11 ` Gene Heskett
[not found] ` <201208241952.04988.tweek@tweek.dk>
2012-08-24 18:18 ` wbrana
2012-08-24 18:35 ` Martin Nybo Andersen
2012-08-24 18:59 ` wbrana
2012-08-24 19:53 ` Martin Nybo Andersen
2012-08-25 8:27 ` wbrana
2012-08-25 8:43 ` Gene Heskett
2012-08-25 9:25 ` wbrana
2012-08-25 12:20 ` wbrana
2012-08-25 14:41 ` wbrana
2012-08-25 15:51 ` Shentino
2012-08-25 16:07 ` wbrana
2012-08-25 11:35 ` Bernd Petrovitsch
2012-08-25 11:52 ` wbrana
2012-08-25 16:46 ` Jochen Striepe
2012-08-25 17:22 ` wbrana
2012-08-25 17:24 ` Shentino
2012-08-25 17:27 ` wbrana
2012-08-25 17:34 ` Pekka Enberg
2012-08-25 17:38 ` wbrana
2012-08-26 2:18 ` Henrique de Moraes Holschuh
2012-08-26 2:30 ` Cruz Julian Bishop
2012-08-27 12:21 ` Bernd Petrovitsch
2012-08-25 17:40 ` Jochen Striepe
2012-08-25 17:49 ` wbrana
2012-08-25 0:51 ` Cruz Julian Bishop
2012-08-25 7:46 ` wbrana
[not found] ` <CANQmPXgefyCJuzFiAugp6OW2+HtjABSWuQqG33gAU_XgQ1V_2A@mail.gmail.com>
2012-08-24 16:19 ` wbrana
2012-08-24 16:36 ` Alan Cox
2012-08-24 16:36 ` wbrana
2012-08-24 16:47 ` Alan Cox
2012-08-24 16:45 ` wbrana
2012-08-26 13:56 ` Mark Lord
[not found] ` <CAJ7jCm=A+OOQNq3HYsyM9bVXYQbfxkXaJg+yN_-vyA+VM9-jgQ@mail.gmail.com>
2012-08-29 23:03 ` Mark Lord
2012-08-29 23:42 ` Jeff Garzik
2012-08-25 0:57 ` Cruz Julian Bishop [this message]
2012-08-23 18:08 ` Al Viro
2012-08-23 18:17 ` wbrana
2012-08-23 18:22 ` Pekka Enberg
2012-08-23 18:23 ` David Daney
2012-08-23 18:30 ` wbrana
2012-08-23 18:33 ` David Daney
2012-08-23 18:40 ` wbrana
2012-08-23 19:01 ` Al Viro
2012-08-24 9:51 ` wbrana
2012-08-23 18:50 ` Martin Nybo Andersen
2012-08-23 18:54 ` Brian Gerst
2012-08-23 19:03 ` wbrana
2012-08-23 19:04 ` Brian Gerst
2012-08-23 19:08 ` wbrana
2012-08-23 19:35 ` Brian Gerst
2012-08-24 9:50 ` wbrana
2012-08-24 10:27 ` Ronnie Collinson
2012-08-24 10:30 ` wbrana
2012-08-24 10:36 ` wbrana
2012-08-24 10:38 ` Ronnie Collinson
2012-08-24 10:42 ` wbrana
2012-08-24 10:49 ` Maarten Lankhorst
2012-08-24 10:59 ` Ronnie Collinson
2012-08-24 11:57 ` Brian Gerst
2012-08-24 9:53 ` wbrana
2012-08-24 12:00 ` Brian Gerst
2012-08-24 12:04 ` wbrana
2012-08-24 12:14 ` Ondrej Zary
2012-08-24 12:27 ` wbrana
2012-08-24 18:17 ` H. Peter Anvin
2012-08-24 18:57 ` Theodore Ts'o
2012-08-24 19:13 ` Alan Cox
2012-08-24 19:58 ` Theodore Ts'o
2012-08-24 20:06 ` Dave Jones
2012-08-24 20:25 ` Borislav Petkov
2012-08-24 20:47 ` H. Peter Anvin
2012-08-24 19:38 ` H. Peter Anvin
2012-08-24 19:40 ` H. Peter Anvin
2012-08-24 20:18 ` Space-Certified CPUs and Linux Craig Milo Rogers
2012-08-24 20:49 ` Drop support for x86-32 Sam Ravnborg
2012-08-30 1:14 ` david
2012-08-24 16:24 ` Raymond Jennings
-- strict thread matches above, loose matches on Subject: below --
2012-08-24 18:09 Martin Nybo Andersen
2012-08-24 19:32 Raymond Jennings
2012-08-26 14:26 Free Email Service
2012-08-26 17:01 ` Shentino
2012-08-26 16:35 Free Email Service
2012-08-28 8:24 Boszormenyi Zoltan
2012-08-30 8:46 Free Email Service
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=503822E6.5040500@gmail.com \
--to=cruzjbishop@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hi3766691@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wbrana@gmail.com \
/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.