linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: linux-kernel@vger.kernel.org, linux-390@vm.marist.edu,
	linux-s390@vger.kernel.org
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: [ANNOUNCE] s390 31 bit kernel support removal
Date: Wed, 12 Feb 2014 10:29:35 +0100	[thread overview]
Message-ID: <20140212092935.GA14964@osiris> (raw)

Hi all,

we plan to remove 31 bit kernel support of the s390 architecture in the
Linux kernel sources.

The reason for this is quite simple: the current 31 bit kernel was broken
for nearly a year before somebody noticed.

Keeping the 31 bit kernel support adds extra maintenance and development
effort which we do not want to spend anymore, especially since the effort
seems to be quite pointless, since nobody uses (and tests) the 31 bit
kernel.

Please note, that we will not remove the 31 bit compatibility layer which
allows to run 31 bit applications with a 64 bit kernel.  It is also
possible to run a complete 31 bit user space distribution with a 64 bit
kernel.

After the removal of the 31 bit kernel support it is not possible to run
new Linux kernels on old 31 bit only machines.  The only supported 31 bit
only machines were the G6 and Multiprise 3000 introduced in 1999.  However
after nearly 15 years it seems reasonable to remove support for these old
machines.

We want to remove s390 31 bit kernel support with Linux kernel 3.16.

Thanks,
Heiko


             reply	other threads:[~2014-02-12  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  9:29 Heiko Carstens [this message]
2014-02-13 10:45 ` [ANNOUNCE] s390 31 bit kernel support removal Michael Tokarev
2014-02-13 10:56   ` Richard Weinberger

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=20140212092935.GA14964@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=linux-390@vm.marist.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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 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).