From: John Garry <john.garry@huawei.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: <satishkh@cisco.com>, <sebaddel@cisco.com>, <kartilak@cisco.com>,
<jejb@linux.ibm.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <hare@suse.de>, <hch@lst.de>,
<bvanassche@acm.org>
Subject: Re: [PATCH 0/3] Remove scsi_cmnd.tag
Date: Wed, 18 Aug 2021 19:08:48 +0100 [thread overview]
Message-ID: <176ce4f2-42c9-bba6-c8f9-70a08faa21b8@huawei.com> (raw)
In-Reply-To: <yq14kbppa42.fsf@ca-mkp.ca.oracle.com>
On 16/08/2021 18:34, Martin K. Petersen wrote:
>
> John,
>
>> There is no need for scsi_cmnd.tag, so remove it.
>
> Applied to 5.15/scsi-staging, thanks!
>
Hi Martin,
As you may have seen, some arm32 build has also broken. My build
coverage was not good enough, and I don't see a point in me playing
whack-a-mole with the kernel test robot. So how about revert the final
patch or even all of them, and I can try get better build coverage and
then re-post? Or maybe you or Bart have a better idea?
Thanks!
next prev parent reply other threads:[~2021-08-18 18:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 13:49 [PATCH 0/3] Remove scsi_cmnd.tag John Garry
2021-08-13 13:49 ` [PATCH 1/3] scsi: wd719: Stop using scsi_cmnd.tag John Garry
2021-08-13 16:30 ` Hannes Reinecke
2021-08-14 3:11 ` Bart Van Assche
2021-08-13 13:49 ` [PATCH 2/3] scsi: fnic: Stop setting scsi_cmnd.tag John Garry
2021-08-13 16:31 ` Hannes Reinecke
2021-08-14 3:17 ` Bart Van Assche
2021-08-14 7:39 ` Christoph Hellwig
2021-08-14 12:35 ` Hannes Reinecke
2021-08-16 10:00 ` John Garry
2021-08-16 11:11 ` Hannes Reinecke
2021-08-13 13:49 ` [PATCH 3/3] scsi: Remove scsi_cmnd.tag John Garry
2021-08-13 16:31 ` Hannes Reinecke
2021-08-14 3:18 ` Bart Van Assche
2021-08-14 7:40 ` [PATCH 0/3] " Christoph Hellwig
2021-08-16 17:34 ` Martin K. Petersen
2021-08-18 18:08 ` John Garry [this message]
2021-08-18 18:46 ` Martin K. Petersen
2021-08-19 2:41 ` Bart Van Assche
2021-08-19 7:15 ` Hannes Reinecke
2021-08-19 7:27 ` John Garry
2021-08-19 7:50 ` Hannes Reinecke
2021-08-19 9:09 ` John Garry
2021-08-24 4:03 ` Martin K. Petersen
2021-08-24 7:54 ` John Garry
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=176ce4f2-42c9-bba6-c8f9-70a08faa21b8@huawei.com \
--to=john.garry@huawei.com \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=kartilak@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.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).