From: "Arnd Bergmann" <arnd@arndb.de>
To: "Bart Van Assche" <bvanassche@acm.org>,
"John Garry" <john.g.garry@oracle.com>,
"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, "Christoph Hellwig" <hch@lst.de>,
"John Garry" <john.garry@linux.dev>,
"Russell King" <linux@armlinux.org.uk>
Subject: Re: [RFC PATCH] scsi: core: Drop Scsi_Host.default_lock
Date: Thu, 06 Aug 2026 00:04:59 +0200 [thread overview]
Message-ID: <eb0c2ccf-08d7-4c4d-a649-db767ddda457@app.fastmail.com> (raw)
In-Reply-To: <559552b3-1336-4fbd-b0cb-6a96ae57b3c3@acm.org>
On Wed, Aug 5, 2026, at 23:47, Bart Van Assche wrote:
> On 8/5/26 6:45 AM, John Garry wrote:
>> I do have to question why we maintain support on modern kernels for such
>> obsolete HW. The maintenance burden is not zero, as we see here ...
>
> (+Arnd)
(+Russell)
> Agreed. From
> https://lore.kernel.org/all/20241204102904.1863796-15-arnd@kernel.org/:
> "ARM: mark RiscPC as deprecated [ ... ] Since there is little hope of
> this being maintainable much longer, plan to remove it in early 2025
> while it is still expected to mostly work."
>
> Arnd, is removal of Acorn RiscPC still planned? That platform relies on
> several SCSI drivers. API changes for the SCSI core, although rare,
> would be easier if we wouldn't have to support the Acorn RiscPC anymore.
I resent my series to deprecate almost all board files recently, and
that is now in linux-next. Unless Russell has any last minute objections,
I would now expect that we can remove all the deprecated files after
7.3-LTS is out, and that includes the drivers/scsi/arm/ directory.
My original plan was to do this all two years earlier, but since we are
close to another LTS kernel, I think it makes sense to wait for that
before removing any code that potentially still works.
Arnd
next prev parent reply other threads:[~2026-08-05 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 11:34 [RFC PATCH] scsi: core: Drop Scsi_Host.default_lock John Garry
2026-08-04 17:53 ` Bart Van Assche
2026-08-04 19:42 ` John Garry
2026-08-04 20:08 ` Bart Van Assche
2026-08-05 13:45 ` John Garry
2026-08-05 21:47 ` Bart Van Assche
2026-08-05 22:04 ` Arnd Bergmann [this message]
2026-08-06 0:35 ` Finn Thain
2026-08-08 1:53 ` Michael Schmitz
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=eb0c2ccf-08d7-4c4d-a649-db767ddda457@app.fastmail.com \
--to=arnd@arndb.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=john.garry@linux.dev \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=martin.petersen@oracle.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).