From: Bart Van Assche <bvanassche@acm.org>
To: Can Guo <quic_cang@quicinc.com>,
Gwendal Grignou <gwendal@chromium.org>,
alim.akhtar@samsung.com, avri.altman@wdc.com,
daejun7.park@samsung.com
Cc: linux-scsi@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] scsi: ufs: core: sysfs: Prevent div by zero
Date: Mon, 25 Nov 2024 15:08:41 -0800 [thread overview]
Message-ID: <4a8d584a-7a0e-4ce8-806e-d6aee65fc378@acm.org> (raw)
In-Reply-To: <fd764f6f-8486-b4c9-26f9-2ff9d903ac7f@quicinc.com>
On 11/21/24 6:12 PM, Can Guo wrote:
> We are the user of the UFS monitor. And we are about to integrate UFS
> queue depth monitoring in it.
Shouldn't such functionality be integrated in the block layer or SCSI
core instead of in the UFS driver such that this functionality becomes
available to all block drivers?
Thanks,
Bart.
next prev parent reply other threads:[~2024-11-25 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 6:25 [PATCH] scsi: ufs: core: sysfs: Prevent div by zero Gwendal Grignou
2024-11-21 20:24 ` Bart Van Assche
2024-11-22 2:12 ` Can Guo
2024-11-25 23:08 ` Bart Van Assche [this message]
2024-11-22 2:09 ` Can Guo
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=4a8d584a-7a0e-4ce8-806e-d6aee65fc378@acm.org \
--to=bvanassche@acm.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=daejun7.park@samsung.com \
--cc=gwendal@chromium.org \
--cc=linux-scsi@vger.kernel.org \
--cc=quic_cang@quicinc.com \
--cc=stable@vger.kernel.org \
/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