linux-oxnas.groups.io archive mirror
 help / color / mirror / Atom feed
From: "Neil Armstrong" <neil.armstrong@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	soc@kernel.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Russell King <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"linux-oxnas@groups.io" <linux-oxnas@groups.io>,
	Linus Walleij <linus.walleij@linaro.org>,
	Daniel Golle <daniel@makrotopia.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH RFC v2 0/4] ARM: oxnas support removal
Date: Tue, 4 Apr 2023 16:43:07 +0200	[thread overview]
Message-ID: <f221954d-66f2-8dac-8e2b-5769c18d9aca@linaro.org> (raw)
In-Reply-To: <86d63038-e3f5-4c03-b904-a26761b0578d@app.fastmail.com>

On 04/04/2023 16:37, Arnd Bergmann wrote:
> On Mon, Apr 3, 2023, at 09:42, Neil Armstrong wrote:
>> With [1] removing MPCore SMP support, this makes the OX820 barely usable,
>> associated with a clear lack of maintainance, development and migration to
>> dt-schema it's clear that Linux support for OX810 and OX820 should be removed.
>>
>> In addition, the OX810 hasn't been booted for years and isn't even present
>> in an ARM config file.
>>
>> For the OX820, lack of USB and SATA support makes the platform not usable
>> in the current Linux support and relies on off-tree drivers hacked from the
>> vendor (defunct for years) sources.
>>
>> The last users are in the OpenWRT distribution, and today's removal means
>> support will still be in stable 6.1 LTS kernel until end of 2026.
>>
>> If someone wants to take over the development even with lack of SMP, I'll
>> be happy to hand off maintainance.
>>
>> The plan is to apply the first 4 patches first, then the drivers
>> followed by bindings. Finally the MAINTAINANCE entry can be removed.
>>
> 
> I merged all four into the soc tree now, thanks!

Thanks for handling this !

Neil

> 
>       Arnd


      reply	other threads:[~2023-04-04 14:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03  7:42 [PATCH RFC v2 0/4] ARM: oxnas support removal Neil Armstrong
2023-04-03  7:42 ` [PATCH RFC v2 1/4] ARM: dts: oxnas: remove obsolete device tree files Neil Armstrong
2023-04-03  7:42 ` [PATCH RFC v2 2/4] ARM: oxnas: remove OXNAS support Neil Armstrong
2023-04-03  7:42 ` [PATCH RFC v2 3/4] ARM: configs: remove oxnas_v6_defconfig Neil Armstrong
2023-04-03  7:42 ` [PATCH RFC v2 4/4] dt-bindings: arm: oxnas: remove obsolete bindings Neil Armstrong
2023-04-03 18:36 ` [PATCH RFC v2 0/4] ARM: oxnas support removal Rob Herring
2023-04-04 14:37 ` Arnd Bergmann
2023-04-04 14:43   ` Neil Armstrong [this message]

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=f221954d-66f2-8dac-8e2b-5769c18d9aca@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=arnd@arndb.de \
    --cc=daniel@makrotopia.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-oxnas@groups.io \
    --cc=linux@armlinux.org.uk \
    --cc=olof@lixom.net \
    --cc=robh+dt@kernel.org \
    --cc=soc@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).