From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: remove ARM710 specific assembler code
Date: Sat, 17 May 2014 10:23:37 +0100 [thread overview]
Message-ID: <20140517092337.GA67711@MacBook-Pro.local> (raw)
In-Reply-To: <20140516125545.GO3693@n2100.arm.linux.org.uk>
On Fri, May 16, 2014 at 01:55:46PM +0100, Russell King - ARM Linux wrote:
> There was a CPU called the ARM710, it was ARMv3 and it had no Thumb support.
>
> There is also a CPU called the ARM710T, which is ARMv4 and has Thumb support.
>
> These are two completely different CPUs, the former was removed along with
> the removal of ARMv3 support. The latter remains because we still support
> ARMv4.
BTW, while clearly this patch was removing code for the wrong reasons, I
think we should set a longer term timeline for getting rid of some of
old features. Let's say in 10 years time we remove everything ARMv4,
another 10 years ARMv5 and so on. We could make these milestones shorter
but it really depends on what people use, we should not force them out
of the kernel if still in use.
We can start with ARM core and SoC code that we suspect people haven't
used in a while (or at least not with mainline). We should not remove
them straight away but give some advanced warning. My proposal is to add
a CONFIG_DEPRECATED option and update it with a 2 year cadence. Code
that we want to remove will depend on DEPRECATED and explicitly not
covered by defconfig. This way we can get interested parties sending
patches to remove the DEPRECATED dependency. Something like this:
config DEPRECATED
bool "Enable deprecated kernel features"
help
Kernel features no longer in use are marked as DEPRECATED for
two years and removed at the end of this period. This option
should only be enabled explicitly and must not be included in
defconfig files. If you think a DEPRECATED kernel feature is
still needed, please contact the corresponding maintainers to
remove the DEPRECATED dependency.
The next scheduled DEPRECATED code removal is planned for 2016.
It would be even better if we make such option across the whole kernel,
especially since we have significant ARM SoC code into drivers.
Otherwise calling it ARM_DEPRECATED would work as well.
--
Catalin
next prev parent reply other threads:[~2014-05-17 9:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 21:46 [PATCH] ARM: remove last use of CONFIG_CPU_ARM710 Paul Bolle
2014-05-14 8:24 ` [PATCH] [RESEND] " Paul Bolle
2014-05-14 8:48 ` Alexander Shiyan
2014-05-14 9:07 ` Paul Bolle
2014-05-14 9:17 ` Arnd Bergmann
2014-05-14 9:25 ` Paul Bolle
2014-05-14 9:28 ` Arnd Bergmann
2014-05-16 9:29 ` [PATCH] ARM: remove ARM710 specific assembler code Paul Bolle
2014-05-16 12:55 ` Russell King - ARM Linux
2014-05-16 14:50 ` Paul Bolle
2014-05-17 9:23 ` Catalin Marinas [this message]
2014-05-17 9:46 ` Russell King - ARM Linux
2014-05-17 9:56 ` Catalin Marinas
2014-05-17 10:26 ` Russell King - ARM Linux
2014-05-19 10:18 ` Catalin Marinas
2014-05-19 11:26 ` Arnd Bergmann
2014-05-20 16:05 ` Tony Lindgren
2014-05-20 20:09 ` Arnd Bergmann
2014-05-22 18:40 ` Tony Lindgren
2014-05-22 18:42 ` Tony Lindgren
2014-05-20 15:48 ` One Thousand Gnomes
2014-05-20 16:14 ` Catalin Marinas
2014-05-23 9:07 ` [PATCH] [RESEND] ARM: remove last use of CONFIG_CPU_ARM710 Paul Bolle
2014-05-23 9:22 ` Arnd Bergmann
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=20140517092337.GA67711@MacBook-Pro.local \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).