linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Russell King <linux@armlinux.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" 
	<linux-samsung-soc@vger.kernel.org>,
	Olof Johansson <olof@lixom.net>, Kukjin Kim <kgene@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Sylwester Nawrocki <snawrocki@kernel.org>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Inki Dae <inki.dae@samsung.com>, Cedric Roux <sed@free.fr>,
	Sam Van Den Berge <sam.van.den.berge@telenet.be>,
	Lihua Yao <ylhuajnu@outlook.com>,
	Heiko Stuebner <heiko@sntech.de>
Subject: Re: [RFC PATCH] ARM: s3c: mark as deprecated and schedule removal after 2022
Date: Tue, 2 Nov 2021 16:36:31 +0100	[thread overview]
Message-ID: <CAK8P3a0J2Md=TefT6ZoiXqP2=tpma+JSfZ3UYmUZKRMNXLh2ig@mail.gmail.com> (raw)
In-Reply-To: <ee51e10d-0fbf-d87f-aa98-a95d97a7e437@canonical.com>

On Tue, Nov 2, 2021 at 3:55 PM Krzysztof Kozlowski
<krzysztof.kozlowski@canonical.com> wrote:
> On 02/11/2021 14:05, Arnd Bergmann wrote:
> > On Tue, Nov 2, 2021 at 12:05 PM Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com> wrote:
> >
> > The ones that would help the most in removing are probably omap1,
> > pxa, and the strongarm-based platforms: those have a lot of special
> > cases in the code base. At least a year ago the maintainers wanted
> > to keep those around, but maybe the 2022 LTS kernel is a better
> > time for planned EOL.
>
> If the maintainers or users expressed wish to keep them alive, let's
> keep them. In fact there might be some industrial machine working for 20
> more years...
>
> If you did not receive any feedback about your queries, I am happy to
> add similar deprecation-warning notes to these as well. Just let me know
> which one should be affected.

There are definitely platforms with long service life, such as ep93xx
or ixp4xx, both of which are actively being worked on. For the other
ones, I think it worth asking again every other year or so, either for
modernising or dropping them in the long run.

> > check around them, I'm fine with it though -- it would still catch all
> > real users without bothering build-testing bots.
>
> I like that idea, I'll use it in v2. No one really should build a real
> config with COMPILE_TEST and I want to nag and find the real users.
>
> > I think even with CONFIG_WERROR, we don't fail the build for #warning,
> > so that would also work in place of #pragma message.
>
> It fails, I tried it. That's why #pragma.

Ok, #pragma with #ifdef is fine then.

       Arnd

  parent reply	other threads:[~2021-11-02 15:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 11:05 [RFC PATCH] ARM: s3c: mark as deprecated and schedule removal after 2022 Krzysztof Kozlowski
2021-11-02 11:09 ` Krzysztof Kozlowski
2021-11-02 13:05 ` Arnd Bergmann
2021-11-02 14:55   ` Krzysztof Kozlowski
2021-11-02 15:00     ` Krzysztof Kozlowski
2021-11-02 15:36     ` Arnd Bergmann [this message]
2021-11-02 16:37 ` Mark Brown
2021-11-03  8:27   ` Krzysztof Kozlowski
2021-11-03 17:05     ` Mark Brown
2021-11-02 17:43 ` Heiko Stübner
2021-11-03  8:34 ` Tomasz Figa
2021-11-05 17:49 ` Cedric Roux
2021-11-06 18:20   ` Krzysztof Kozlowski
2021-11-06 19:33     ` Heiko Stübner
2021-11-06 20:13       ` Arnd Bergmann
2021-11-07  9:11         ` Krzysztof Kozlowski

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='CAK8P3a0J2Md=TefT6ZoiXqP2=tpma+JSfZ3UYmUZKRMNXLh2ig@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=cw00.choi@samsung.com \
    --cc=heiko@sntech.de \
    --cc=inki.dae@samsung.com \
    --cc=kgene@kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=olof@lixom.net \
    --cc=sam.van.den.berge@telenet.be \
    --cc=sed@free.fr \
    --cc=snawrocki@kernel.org \
    --cc=tomasz.figa@gmail.com \
    --cc=ylhuajnu@outlook.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).