From: John Garry <john.g.garry@oracle.com>
To: jejb@linux.ibm.com, martin.petersen@oracle.com,
chenxiang66@hisilicon.com, jinpu.wang@cloud.ionos.com,
artur.paszkiewicz@intel.com, yanaijie@huawei.com,
dlemoal@kernel.org, ipylypiv@google.com, cassel@kernel.org
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
John Garry <john.g.garry@oracle.com>
Subject: [PATCH v2 0/6] Add LIBSAS_SHT_BASE for libsas
Date: Fri, 8 Mar 2024 11:43:33 +0000 [thread overview]
Message-ID: <20240308114339.1340549-1-john.g.garry@oracle.com> (raw)
There is much duplication in the scsi_host_template structure for the
drivers which use libsas.
Similar to how a standard template is used in libata with __ATA_BASE_SHT,
create a standard template in LIBSAS_SHT_BASE.
Based on following:
b914227e4215 (tag: mkp-scsi-staging, mkp-scsi/staging, mkp-scsi/for-next, mkp-scsi/6.9/scsi-staging) Merge patch series "Pass data lifetime information to SCSI disk devices"
Differences to v1:
- tidy libsas.h change (Jason)
- Don't set eh_abort_handler in LIBSAS_SHT_BASE (Jason)
- Remove sg_tablesize in LIBSAS_SHT_BASE, as W=1 build dislikes it
- Add some RB tags (Thanks)
John Garry (6):
scsi: libsas: Add LIBSAS_SHT_BASE
scsi: pm8001: Use LIBSAS_SHT_BASE
scsi: hisi_sas: Use LIBSAS_SHT_BASE_NO_SLAVE_INIT
scsi: aic94xx: Use LIBSAS_SHT_BASE
scsi: mvsas: Use LIBSAS_SHT_BASE
scsi: isci: Use LIBSAS_SHT_BASE
drivers/scsi/aic94xx/aic94xx_init.c | 21 ++-----------------
drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 18 +---------------
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 18 +---------------
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 18 +---------------
drivers/scsi/isci/init.c | 23 ++------------------
drivers/scsi/mvsas/mv_init.c | 19 +----------------
drivers/scsi/pm8001/pm8001_init.c | 20 +-----------------
include/scsi/libsas.h | 29 ++++++++++++++++++++++++++
8 files changed, 38 insertions(+), 128 deletions(-)
--
2.31.1
next reply other threads:[~2024-03-08 11:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 11:43 John Garry [this message]
2024-03-08 11:43 ` [PATCH v2 1/6] scsi: libsas: Add LIBSAS_SHT_BASE John Garry
2024-03-08 19:41 ` Igor Pylypiv
2024-03-10 10:02 ` John Garry
2024-03-10 20:05 ` Igor Pylypiv
2024-03-08 11:43 ` [PATCH v2 2/6] scsi: pm8001: Use LIBSAS_SHT_BASE John Garry
2024-03-10 20:17 ` Igor Pylypiv
2024-03-11 1:57 ` Jason Yan
2024-03-08 11:43 ` [PATCH v2 3/6] scsi: hisi_sas: Use LIBSAS_SHT_BASE_NO_SLAVE_INIT John Garry
2024-03-10 20:19 ` Igor Pylypiv
2024-03-08 11:43 ` [PATCH v2 4/6] scsi: aic94xx: Use LIBSAS_SHT_BASE John Garry
2024-03-10 20:22 ` Igor Pylypiv
2024-03-08 11:43 ` [PATCH v2 5/6] scsi: mvsas: " John Garry
2024-03-10 20:24 ` Igor Pylypiv
2024-03-11 2:04 ` Jason Yan
2024-03-08 11:43 ` [PATCH v2 6/6] scsi: isci: " John Garry
2024-03-10 20:25 ` Igor Pylypiv
2024-03-11 1:46 ` [PATCH v2 0/6] Add LIBSAS_SHT_BASE for libsas Jason Yan
2024-03-11 7:41 ` John Garry
2024-03-25 20:11 ` Martin K. Petersen
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=20240308114339.1340549-1-john.g.garry@oracle.com \
--to=john.g.garry@oracle.com \
--cc=artur.paszkiewicz@intel.com \
--cc=cassel@kernel.org \
--cc=chenxiang66@hisilicon.com \
--cc=dlemoal@kernel.org \
--cc=ipylypiv@google.com \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=yanaijie@huawei.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).