Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Cc: Russell King <rmk+kernel@armlinux.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Krzysztof Halasa <khalasa@piap.pl>,
	Daniel Mack <daniel@zonque.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Robert Jarzmik <robert.jarzmik@free.fr>,
	Marek Vasut <marek.vasut@gmail.com>,
	Lubomir Rintel <lkundrak@v3.sk>,
	Alexander Sverdlin <alexander.sverdlin@gmail.com>,
	Hartley Sweeten <hsweeten@visionengravers.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Sekhar Nori <nsekhar@ti.com>, Bartosz Golaszewski <brgl@bgdev.pl>,
	Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Gregory CLEMENT <gregory.clement@bootlin.com>,
	Lennert Buytenhek <kernel@wantstofly.org>,
	Marc Zyngier <maz@kernel.org>,
	Mauri Sandberg <maukka@ext.kapsi.fi>
Subject: Re: Scheduling (unused) board file removal for linux-6.x
Date: Thu, 30 Jun 2022 09:10:32 +0200	[thread overview]
Message-ID: <1413e8b9-5e55-e121-926e-38cb66d152ee@kernel.org> (raw)
In-Reply-To: <CAK8P3a0Z9vGEQbVRBo84bSyPFM-LF+hs5w8ZA51g2Z+NsdtDQA@mail.gmail.com>

On 29/06/2022 22:42, Arnd Bergmann wrote:
> With the multiplatform work completed in the past merge window, and the
> scheduled deprecation of the Samsung s3c platforms, I decided to have a
> look at the remaining board files. There are 196 remaining boards, down
> from 489 boards ten years ago, but my estimate is that only few of those
> ever booted a linux-5.x kernel, and even less for future kernels. The
> question is how to find out which ones are still used, and which ones
> can go.
> 
> I would propose that we start by changing the assumption that all boards
> might be used, instead assuming that they are all outdated unless someone
> says that they actually prefer to keep it in the kernel.  I have started
> a list of all 196 boards and annotated the ones that look like candidates
> for removal [1]. If a board you use is on that list, please either reply
> here or add a comment in the document.
> 
> Unless someone has a better idea for how to proceed, I would allow
> six months for users to speak up and then remove the orphaned board
> files for the release following the LTS kernel. I can't list all boards
> individually, so here is a breakdown by platform:
> 
> s3c24xx
> 
> These are all scheduled for removal in early 2023 already, once the next
> longterm stable kernel is out. No changes here, but it seems useful
> to use the same timeline for removing unused board files of the other
> platforms together.
> 
> s3c64xx
> 
> There are ten board files, which are currently scheduled for removal in
> 2024, along with the DT based boards for this SoC. We can still decide
> to throw out some of the board files earlier though, while keeping the
> platform around.

I would keep all s3c24xx/s3c64xx boards till the platform drop. Removing
few boards before platform won't give us huge benefits... and anyway
just 1 and 2 years and they all will be gone.

Best regards,
Krzysztof

  parent reply	other threads:[~2022-06-30  7:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 20:42 Scheduling (unused) board file removal for linux-6.x Arnd Bergmann
2022-06-29 20:59 ` Alexander Sverdlin
2022-06-30  7:42   ` Arnd Bergmann
2022-07-03 11:24     ` Alexander Sverdlin
2022-07-03 16:11       ` Arnd Bergmann
2022-07-04  9:07         ` Nikita Shubin
2022-06-29 22:53 ` Rob Herring
2022-06-30  7:57   ` Arnd Bergmann
2022-06-30  6:59 ` Marc Zyngier
2022-06-30  7:10 ` Tony Lindgren
2022-06-30  7:10 ` Krzysztof Kozlowski [this message]
2022-06-30  9:08   ` Arnd Bergmann
2022-06-30  9:22     ` Krzysztof Kozlowski
2022-06-30 12:10       ` Arnd Bergmann
2022-06-30 17:00         ` Krzysztof Kozlowski
2022-07-01  2:05           ` Tomasz Figa
2022-06-30  9:39 ` Krzysztof Hałasa
2022-06-30 11:32 ` Linus Walleij
2022-07-01 10:21   ` Daniel Mack
2022-07-01 10:53   ` Arnd Bergmann
2022-07-01 11:26     ` Alexander Sverdlin
2022-07-01 11:43     ` Linus Walleij
2022-07-01 12:28       ` Arnd Bergmann
2022-07-02  9:47     ` Christoph Hellwig
2022-07-02 10:06       ` Arnd Bergmann
2022-07-03  7:13         ` Christoph Hellwig

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=1413e8b9-5e55-e121-926e-38cb66d152ee@kernel.org \
    --to=krzk@kernel.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=alexander.sverdlin@gmail.com \
    --cc=alim.akhtar@samsung.com \
    --cc=andrew@lunn.ch \
    --cc=arnd@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=daniel@zonque.org \
    --cc=gregory.clement@bootlin.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=hsweeten@visionengravers.com \
    --cc=kernel@wantstofly.org \
    --cc=khalasa@piap.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --cc=marek.vasut@gmail.com \
    --cc=maukka@ext.kapsi.fi \
    --cc=maz@kernel.org \
    --cc=nsekhar@ti.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robert.jarzmik@free.fr \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=tony@atomide.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