From: Bart Van Assche <bvanassche@acm.org>
To: Thomas Yen <thomasyen@google.com>
Cc: Stable Tree <stable@vger.kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Peter Wang <peter.wang@mediatek.com>,
Bean Huo <beanhuo@micron.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
"open list:UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER"
<linux-scsi@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/1] scsi: ufs: core: Flush exception handling work when RPM level is zero
Date: Thu, 29 Jan 2026 09:23:38 -0800 [thread overview]
Message-ID: <076fe171-6fd3-4dbc-9876-242905379594@acm.org> (raw)
In-Reply-To: <CALw5pqG735L-6-umZspQOKB9DfRHf7D0AfpkRD_=xwX0LtZ2Vg@mail.gmail.com>
On 1/29/26 9:19 AM, Thomas Yen wrote:
> I had just sent v4 (to add the missing Fixes tag) before seeing this
> message. Since the code logic in v4 is identical to v3, I hope that is
> acceptable.
It seems like our emails crossed each other. This is something that can
happen.
When reposting a patch, Reviewed-by tags should be included. I don't see
any Reviewed-by tags in v4 of this patch although Peter Wang had posted
a Reviewed-by?
Thanks,
Bart.
next prev parent reply other threads:[~2026-01-29 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 7:06 [PATCH v3 1/1] scsi: ufs: core: Flush exception handling work when RPM level is zero Thomas Yen
2026-01-29 13:42 ` Peter Wang (王信友)
2026-01-29 14:08 ` [PATCH v3] " Markus Elfring
2026-01-29 17:04 ` [PATCH v3 1/1] " Bart Van Assche
2026-01-29 17:19 ` Thomas Yen
2026-01-29 17:23 ` Bart Van Assche [this message]
2026-01-29 17:39 ` Thomas Yen
2026-01-30 22:58 ` Bart Van Assche
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=076fe171-6fd3-4dbc-9876-242905379594@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=quic_nguyenb@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=thomasyen@google.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