From: Damien Le Moal <dlemoal@kernel.org>
To: linux-ide@vger.kernel.org, Niklas Cassel <cassel@kernel.org>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: [PATCH v1 0/9] ATA support for storage element management commands
Date: Mon, 6 Jul 2026 15:56:01 +0900 [thread overview]
Message-ID: <20260706065610.3559692-1-dlemoal@kernel.org> (raw)
This patch series adds support to libata for translating all storage
element management commands:
- GET PHYSICAL ELEMENT STATUS
- REMOVE ELEMENT AND TRUNCATE
- RESTORE ELEMENTS AND REBUILD
- REMOVE ELEMENT AND MODIFY ZONES
The first 2 patches add definitions to scsi_proto.h related to the
depopulation feature. The remaining patches modify libata to detect
support for this feature and add command translation support.
Martin,
I have more patches for sd and scsi_debug (depop emulation) that depend on
patch 1 & 2. So I am not sure how we should handle this series. Maybe we
should create a "depop" topic branch in the scsi or libata tree ? I am
open to suggestions.
Damien Le Moal (9):
scsi: scsi_debug: move ASC and ASCQ definitions to scsi_proto.h
scsi: define depopulation capabilities related service actions
ata: libata: improve the definition of device flags
ata: libata-scsi: improve ata_get_xlat_func
ata: libata-core: detect support for depopulation capabilities
ata: libata-scsi: add support for the GET PHYSICAL ELEMENT STATUS
command
ata: libata-scsi: add support for the REMOVE ELEMENT AND TRUNCATE
command
ata: libata-scsi: add support for the RESTORE ELEMENTS AND REBUILD
command
ata: libata-scsi: add support for the REMOVE ELEMENT AND MODIFY ZONES
command
drivers/ata/libata-core.c | 73 +++++++++-
drivers/ata/libata-scsi.c | 300 +++++++++++++++++++++++++++++++++++++-
drivers/scsi/scsi_debug.c | 46 ------
include/linux/ata.h | 4 +
include/linux/libata.h | 90 +++++++-----
include/scsi/scsi_proto.h | 74 ++++++++++
6 files changed, 493 insertions(+), 94 deletions(-)
--
2.54.0
next reply other threads:[~2026-07-06 6:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 6:56 Damien Le Moal [this message]
2026-07-06 6:56 ` [PATCH v1 1/9] scsi: scsi_debug: move ASC and ASCQ definitions to scsi_proto.h Damien Le Moal
2026-07-06 8:29 ` Hannes Reinecke
2026-07-06 8:55 ` Damien Le Moal
2026-07-06 8:44 ` Hannes Reinecke
2026-07-06 9:00 ` Damien Le Moal
2026-07-06 6:56 ` [PATCH v1 2/9] scsi: define depopulation capabilities related service actions Damien Le Moal
2026-07-06 6:56 ` [PATCH v1 3/9] ata: libata: improve the definition of device flags Damien Le Moal
2026-07-06 6:56 ` [PATCH v1 4/9] ata: libata-scsi: improve ata_get_xlat_func Damien Le Moal
2026-07-06 6:56 ` [PATCH v1 5/9] ata: libata-core: detect support for depopulation capabilities Damien Le Moal
2026-07-06 6:56 ` [PATCH v1 6/9] ata: libata-scsi: add support for the GET PHYSICAL ELEMENT STATUS command Damien Le Moal
2026-07-06 6:56 ` [PATCH v1 7/9] ata: libata-scsi: add support for the REMOVE ELEMENT AND TRUNCATE command Damien Le Moal
2026-07-06 6:56 ` [PATCH v1 8/9] ata: libata-scsi: add support for the RESTORE ELEMENTS AND REBUILD command Damien Le Moal
2026-07-06 6:56 ` [PATCH v1 9/9] ata: libata-scsi: add support for the REMOVE ELEMENT AND MODIFY ZONES command Damien Le Moal
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=20260706065610.3559692-1-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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