From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev@lists.ozlabs.org
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Anton Blanchard <anton@au1.ibm.com>,
Paul Mackerras <pmac@au1.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [RFC] Removing support for legacy iSeries
Date: Thu, 02 Feb 2012 13:36:14 +1100 [thread overview]
Message-ID: <1328150174.28487.100.camel@pasglop> (raw)
So I (and Stephen) believe the time has come that we get rid of the
legacy iSeries support in the kernel....
Is there any objection ? Do we have any user left ?
The hypervisor on these is really nasty, and removing support for it
would allow us to clean up quite a bit of code path including low level
& asm ones from iSeries special cases.
Also it's becoming increasingly hard for me to test that we are still
capable of booting these.
I will keep it if we have users but since distros don't support it
anymore (and haven't for a while now) I am pretty keen.
Any objection ?
Cheers,
Ben.
reply other threads:[~2012-02-02 2:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1328150174.28487.100.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=anton@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pmac@au1.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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).