From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: linux@armlinux.org.uk, John Garry <john.garry@huawei.com>,
hare@suse.de, jejb@linux.ibm.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/3] scsi: remove last references to scsi_cmnd.tag
Date: Wed, 22 Sep 2021 00:44:51 -0400 [thread overview]
Message-ID: <163228551952.26896.5878397565348027959.b4-ty@oracle.com> (raw)
In-Reply-To: <1631696835-136198-1-git-send-email-john.garry@huawei.com>
On Wed, 15 Sep 2021 17:07:12 +0800, John Garry wrote:
> This is v2 of Hannes' series to fix the build errors from removing
> scsi_cmnd.tag. Here is the original cover letter:
>
> "with commit 4c7b6ea336c1 ("scsi: core: Remove scsi_cmnd.tag") drivers
> cannot reference the SCSI command tag anymore.
> Arguably these drivers would have stopped working since 2010 with
> the switch to block layer tags in SCSI anyway, so chances are no-one
> had been using tagging in these drivers.
>
> [...]
Applied to 5.15/scsi-fixes, thanks!
[1/3] fas216: kill scmd->tag
https://git.kernel.org/mkp/scsi/c/bc41fcbffd57
[2/3] acornscsi: remove tagged queuing vestiges
https://git.kernel.org/mkp/scsi/c/756fb6a895af
[3/3] scsi: remove 'current_tag'
https://git.kernel.org/mkp/scsi/c/a4869faf9642
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-09-22 4:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 9:07 [PATCH v2 0/3] scsi: remove last references to scsi_cmnd.tag John Garry
2021-09-15 9:07 ` [PATCH v2 1/3] fas216: kill scmd->tag John Garry
2021-09-15 9:07 ` [PATCH v2 2/3] acornscsi: remove tagged queuing vestiges John Garry
2021-09-30 7:21 ` Arnd Bergmann
2021-09-30 8:17 ` John Garry
2021-10-12 23:45 ` Bart Van Assche
2021-09-15 9:07 ` [PATCH v2 3/3] scsi: remove 'current_tag' John Garry
2021-09-16 2:52 ` Bart Van Assche
2021-09-22 4:44 ` Martin K. Petersen [this message]
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=163228551952.26896.5878397565348027959.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=hare@suse.de \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).