From: Wenchao Hao <haowenchao22@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Wenchao Hao <haowenchao2@huawei.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] SCSI: Fix issues between removing device and error handle
Date: Wed, 18 Oct 2023 22:40:26 +0800 [thread overview]
Message-ID: <CAOptpSMnGyc5cjkxuHvLCsv_DaS8e9maCkCyp=vGne6KDX43eg@mail.gmail.com> (raw)
In-Reply-To: <3e7cd38f-681b-446d-9c16-a694a8d03497@acm.org>
On Wed, Oct 18, 2023 at 9:51 PM Bart Van Assche <bvanassche@acm.org> wrote:
>
> On 10/17/23 18:37, Wenchao Hao wrote:
> > The previous version was posted on 2023/9/28 but not reviewed, so I
> > ping soon after repost.
>
> Since a repost counts as a ping, I think posting a ping soon after
> reposting is considered aggressive.
>
I didn't mean that, then how long is appropriate to post a ping?
Thanks.
> Bart.
next prev parent reply other threads:[~2023-10-18 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 2:03 [PATCH v3 0/4] SCSI: Fix issues between removing device and error handle Wenchao Hao
2023-10-16 2:03 ` [PATCH v3 1/4] scsi: core: Add new helper to iterate all devices of host Wenchao Hao
2023-10-17 15:31 ` kernel test robot
2023-10-16 2:03 ` [PATCH v3 2/4] scsi: scsi_error: Fix wrong statistic when print error info Wenchao Hao
2023-10-16 2:03 ` [PATCH v3 3/4] scsi: scsi_error: Fix device reset is not triggered Wenchao Hao
2023-10-16 2:03 ` [PATCH v3 4/4] scsi: scsi_core: Fix IO hang when device removing Wenchao Hao
2023-11-14 21:23 ` Mike Christie
2023-11-14 21:47 ` Mike Christie
2023-11-15 16:24 ` Wenchao Hao
2024-03-07 14:36 ` Wenchao Hao
2023-10-17 17:00 ` [PATCH v3 0/4] SCSI: Fix issues between removing device and error handle Wenchao Hao
2023-10-17 21:41 ` Bart Van Assche
2023-10-18 1:37 ` Wenchao Hao
2023-10-18 13:51 ` Bart Van Assche
2023-10-18 14:40 ` Wenchao Hao [this message]
2023-10-18 18:03 ` Bart Van Assche
2023-11-13 16:00 ` 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='CAOptpSMnGyc5cjkxuHvLCsv_DaS8e9maCkCyp=vGne6KDX43eg@mail.gmail.com' \
--to=haowenchao22@gmail.com \
--cc=bvanassche@acm.org \
--cc=haowenchao2@huawei.com \
--cc=jejb@linux.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.