From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, 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:37:59 +0000 [thread overview]
Message-ID: <YYFpZ9zh5++xl6nr@sirena.org.uk> (raw)
In-Reply-To: <20211102110519.142434-1-krzysztof.kozlowski@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Tue, Nov 02, 2021 at 12:05:19PM +0100, Krzysztof Kozlowski wrote:
> Let's mark all S3C24xx and S3C64xx platforms as deprecated and mention
> possible removal in one year (after 2022). The deprecation message will
> be as text in Kconfig, build message (not a warning though) and runtime
> print error.
>
> If there are any users, they might respond and postpone the removal.
The Speyside system is s3c64xx based, I'm in the middle of reorganising
my hardware setup so it's not usable right now but it's quite useful.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, 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:37:59 +0000 [thread overview]
Message-ID: <YYFpZ9zh5++xl6nr@sirena.org.uk> (raw)
In-Reply-To: <20211102110519.142434-1-krzysztof.kozlowski@canonical.com>
[-- Attachment #1.1: Type: text/plain, Size: 535 bytes --]
On Tue, Nov 02, 2021 at 12:05:19PM +0100, Krzysztof Kozlowski wrote:
> Let's mark all S3C24xx and S3C64xx platforms as deprecated and mention
> possible removal in one year (after 2022). The deprecation message will
> be as text in Kconfig, build message (not a warning though) and runtime
> print error.
>
> If there are any users, they might respond and postpone the removal.
The Speyside system is s3c64xx based, I'm in the middle of reorganising
my hardware setup so it's not usable right now but it's quite useful.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-02 16:38 UTC|newest]
Thread overview: 32+ 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:05 ` Krzysztof Kozlowski
2021-11-02 11:09 ` Krzysztof Kozlowski
2021-11-02 11:09 ` Krzysztof Kozlowski
2021-11-02 13:05 ` Arnd Bergmann
2021-11-02 13:05 ` Arnd Bergmann
2021-11-02 14:55 ` Krzysztof Kozlowski
2021-11-02 14:55 ` Krzysztof Kozlowski
2021-11-02 15:00 ` Krzysztof Kozlowski
2021-11-02 15:00 ` Krzysztof Kozlowski
2021-11-02 15:36 ` Arnd Bergmann
2021-11-02 15:36 ` Arnd Bergmann
2021-11-02 16:37 ` Mark Brown [this message]
2021-11-02 16:37 ` Mark Brown
2021-11-03 8:27 ` Krzysztof Kozlowski
2021-11-03 8:27 ` Krzysztof Kozlowski
2021-11-03 17:05 ` Mark Brown
2021-11-03 17:05 ` Mark Brown
2021-11-02 17:43 ` Heiko Stübner
2021-11-02 17:43 ` Heiko Stübner
2021-11-03 8:34 ` Tomasz Figa
2021-11-03 8:34 ` Tomasz Figa
2021-11-05 17:49 ` Cedric Roux
2021-11-05 17:49 ` Cedric Roux
2021-11-06 18:20 ` Krzysztof Kozlowski
2021-11-06 18:20 ` Krzysztof Kozlowski
2021-11-06 19:33 ` Heiko Stübner
2021-11-06 19:33 ` Heiko Stübner
2021-11-06 20:13 ` Arnd Bergmann
2021-11-06 20:13 ` Arnd Bergmann
2021-11-07 9:11 ` Krzysztof Kozlowski
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=YYFpZ9zh5++xl6nr@sirena.org.uk \
--to=broonie@kernel.org \
--cc=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 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.