From: John Garry <john.garry@huawei.com>
To: <damien.lemoal@opensource.wdc.com>, <hch@lst.de>
Cc: <linux-kernel@vger.kernel.org>, <linux-ide@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
John Garry <john.garry@huawei.com>
Subject: [PATCH v2 0/2] libata: A tagging improvement and related code reorg
Date: Mon, 4 Apr 2022 22:53:08 +0800 [thread overview]
Message-ID: <1649083990-207133-1-git-send-email-john.garry@huawei.com> (raw)
This is a follow-up to the series at [0] to fix SCSI device tagging and
use the per-device token as the libata qc tag.
I added the changes Christoph shared on the list to move
the functionality from ata_qc_new_init() into libata-scsi.c
Please do not apply on a kernel which does not include
"scsi: core: Fix sbitmap depth in scsi_realloc_sdev_budget_map()"
v5.18-rc2 should be the release to include that patch.
[0] https://lore.kernel.org/linux-ide/1647340746-17600-1-git-send-email-john.garry@huawei.com/
Christoph Hellwig (1):
libata: Inline ata_qc_new_init() in ata_scsi_qc_new()
John Garry (1):
libata: Use scsi cmnd budget token for qc tag for SAS host
Documentation/driver-api/libata.rst | 11 -------
drivers/ata/libata-core.c | 48 +----------------------------
drivers/ata/libata-sata.c | 25 ---------------
drivers/ata/libata-scsi.c | 45 ++++++++++++++++++++-------
drivers/ata/libata.h | 13 --------
include/linux/libata.h | 1 -
6 files changed, 35 insertions(+), 108 deletions(-)
--
2.26.2
next reply other threads:[~2022-04-04 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 14:53 John Garry [this message]
2022-04-04 14:53 ` [PATCH v2 1/2] libata: Use scsi cmnd budget token for qc tag for SAS host John Garry
2022-04-06 1:39 ` Damien Le Moal
2022-04-06 7:12 ` John Garry
2022-04-06 8:10 ` Damien Le Moal
2022-04-04 14:53 ` [PATCH v2 2/2] libata: Inline ata_qc_new_init() in ata_scsi_qc_new() John Garry
2022-04-05 5:52 ` Christoph Hellwig
2022-04-06 1:48 ` Damien Le Moal
2022-04-06 7:16 ` John Garry
2022-04-06 8:10 ` Damien Le Moal
2022-04-06 8:11 ` Christoph Hellwig
2022-04-06 1:47 ` 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=1649083990-207133-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@lst.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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 NNTP newsgroup(s).