From: Wenchao Hao <haowenchao22@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>,
Wenchao Hao <haowenchao2@huawei.com>,
linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
"James E. J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] SCSI: Fix issues between removing device and error handle
Date: Wed, 17 Apr 2024 23:00:34 +0800 [thread overview]
Message-ID: <b55da065-dbbb-4d8e-8baf-50807b507cc4@gmail.com> (raw)
In-Reply-To: <99598b98-8550-4dca-beea-4c2d61d46f78@web.de>
On 4/15/24 11:07 PM, Markus Elfring wrote:
> …
>> These issues are triggered because devices in removing would be skipped
>> when calling shost_for_each_device().
> …
>
> How do you think about to add the tag “Fixes” to any of your patches?
>
Thanks for your suggestion, but I don't know how to add this tag. Could you
please tell me how to do?
I just added "fix" in my cover letter and some patch's subject.
> Regards,
> Markus
>
next prev parent reply other threads:[~2024-04-17 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 14:43 [PATCH v4 0/3] SCSI: Fix issues between removing device and error handle Wenchao Hao
2024-03-07 14:43 ` [PATCH v4 1/3] scsi: core: Add new helper to iterate all devices of host Wenchao Hao
2024-03-07 14:43 ` [PATCH v4 2/3] scsi: scsi_error: Fix wrong statistic when print error info Wenchao Hao
2024-03-07 14:43 ` [PATCH v4 3/3] scsi: scsi_error: Fix device reset is not triggered Wenchao Hao
2024-03-26 6:37 ` [PATCH v4 0/3] SCSI: Fix issues between removing device and error handle Wenchao Hao
2024-04-12 2:07 ` Wenchao Hao
2024-04-15 15:07 ` Markus Elfring
2024-04-17 15:00 ` Wenchao Hao [this message]
2024-04-17 15:06 ` Julia Lawall
2024-04-17 15:18 ` Wenchao Hao
2024-04-17 15:29 ` Wenchao Hao
2024-04-17 15:48 ` [v4 " Markus Elfring
2024-04-17 16:39 ` Wenchao Hao
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=b55da065-dbbb-4d8e-8baf-50807b507cc4@gmail.com \
--to=haowenchao22@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=haowenchao2@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).