From: Michael Ellerman <mpe@kernel.org>
To: Andrew Donnellan <ajd@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, fbarrat@linux.ibm.com,
ukrishn@linux.ibm.com, manoj@linux.ibm.com,
clombard@linux.ibm.com, vaibhav@linux.ibm.com
Subject: Re: [PATCH 0/2] Remove cxl and cxlflash drivers
Date: Tue, 17 Dec 2024 14:26:04 +1100 [thread overview]
Message-ID: <87y10f2do3.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20241210072721.157323-1-ajd@linux.ibm.com>
Andrew Donnellan <ajd@linux.ibm.com> writes:
> This series removes the cxl and cxlflash drivers for IBM CAPI devices.
>
> CAPI devices have been out of production for some time, and we're not
> aware of any remaining users who are likely to want a modern kernel.
> There's almost certainly some remaining driver bugs and we don't have much
> hardware available to properly test the drivers any more. Removing these
> drivers will also mean we can get rid of a non-trivial amount of support
> code in arch/powerpc.
>
> Thanks to everyone who's worked on these drivers over the last decade.
It would be good to explain that this only removes support for the
original CAPI interface - not the Power9 "OpenCAPI", which is still
supported by drivers/misc/ocxl.
cheers
next prev parent reply other threads:[~2024-12-17 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 7:27 [PATCH 0/2] Remove cxl and cxlflash drivers Andrew Donnellan
2024-12-10 7:27 ` [PATCH 1/2] cxlflash: Remove driver Andrew Donnellan
2024-12-10 15:30 ` Frederic Barrat
2024-12-10 7:27 ` [PATCH 2/2] cxl: " Andrew Donnellan
2024-12-10 15:29 ` Frederic Barrat
2024-12-17 3:26 ` Michael Ellerman [this message]
2024-12-17 3:37 ` [PATCH 0/2] Remove cxl and cxlflash drivers Andrew Donnellan
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=87y10f2do3.fsf@mpe.ellerman.id.au \
--to=mpe@kernel.org \
--cc=ajd@linux.ibm.com \
--cc=clombard@linux.ibm.com \
--cc=fbarrat@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manoj@linux.ibm.com \
--cc=ukrishn@linux.ibm.com \
--cc=vaibhav@linux.ibm.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).