From: Bart Van Assche <bvanassche@acm.org>
To: "Bo Ye (叶波)" <Bo.Ye@mediatek.com>,
"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>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Cc: "Xiujuan Tan (谭秀娟)" <xiujuan.tan@mediatek.com>,
"Qilin Tan (谭麒麟)" <Qilin.Tan@mediatek.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>
Subject: Re: 回覆: [PATCH] scsi: ufs: preventing bus hang crash during emergency power off
Date: Mon, 7 Jul 2025 08:39:50 -0700 [thread overview]
Message-ID: <9f281874-21b7-4561-914a-52c8ef16b03a@acm.org> (raw)
In-Reply-To: <SEYPR03MB6531CD4D3FAD80339F8E693B944FA@SEYPR03MB6531.apcprd03.prod.outlook.com>
On 7/7/25 12:49 AM, Bo Ye (叶波) wrote:
> Thank you for your feedback.
> I believe ufshcd_wait_for_doorbell_clr() can handle both legacy single
> doorbell mode and MCQ [ ... ]
Agreed.
> Therefore, the current implementation should support both modes.
> Please let me know if you have further concerns.
The Fixes tag seems wrong to me. I think it should be changed into the
following:
Fixes: 19a198b67767 ("scsi: ufs: core: Set SDEV_OFFLINE when UFS is shut
down")
I will add more comments as a reply to the original patch.
Bart.
next prev parent reply other threads:[~2025-07-07 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 7:38 Bo Ye
2025-05-19 15:31 ` Bart Van Assche
2025-06-24 16:14 ` Bart Van Assche
[not found] ` <SEYPR03MB6531CD4D3FAD80339F8E693B944FA@SEYPR03MB6531.apcprd03.prod.outlook.com>
2025-07-07 15:39 ` Bart Van Assche [this message]
2025-07-07 16:14 ` 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=9f281874-21b7-4561-914a-52c8ef16b03a@acm.org \
--to=bvanassche@acm.org \
--cc=Bo.Ye@mediatek.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Qilin.Tan@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=xiujuan.tan@mediatek.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
all inboxes | Powered by JetHome®