From: Bart Van Assche <bvanassche@acm.org>
To: Manivannan Sadhasivam <mani@kernel.org>,
Nitin Rawat <quic_nitirawa@quicinc.com>
Cc: James.Bottomley@hansenpartnership.com,
martin.petersen@oracle.com, avri.altman@wdc.com,
ebiggers@google.com, neil.armstrong@linaro.org,
konrad.dybcio@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
"Bao D. Nguyen" <quic_nguyenb@quicinc.com>
Subject: Re: [PATCH V2 1/3] scsi: ufs: ufs-qcom: Update esi_vec_mask for HW major version >= 6
Date: Tue, 8 Jul 2025 09:18:42 -0700 [thread overview]
Message-ID: <5a1bd678-c935-4c1b-812d-a249f1caebb7@acm.org> (raw)
In-Reply-To: <ldid3ptehto2kmzyixih73vc7tszwdiitr74rnwklxeeekwxrn@mm7zmyfickda>
On 7/8/25 12:53 AM, Manivannan Sadhasivam wrote:
> On Tue, Jul 08, 2025 at 02:32:58AM GMT, Nitin Rawat wrote:
>> From: "Bao D. Nguyen" <quic_nguyenb@quicinc.com>
>
> Nit: Please use consistent subject prefix:
>
> scsi: ufs: qcom:
>
> Maybe we should get rid of 'scsi' prefix since the ufs code is now moved
> outside of drivers/scsi/. Bart?
Dropping the "scsi:" prefix sounds good to me because this prefix makes
patch subject lines a bit long.
Thanks,
Bart.
next prev parent reply other threads:[~2025-07-08 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 21:02 [PATCH V2 0/3] scsi: ufs: qcom: Align programming sequence as per HW spec Nitin Rawat
2025-07-07 21:02 ` [PATCH V2 1/3] scsi: ufs: ufs-qcom: Update esi_vec_mask for HW major version >= 6 Nitin Rawat
2025-07-08 7:51 ` Manivannan Sadhasivam
2025-07-08 7:53 ` Manivannan Sadhasivam
2025-07-08 16:18 ` Bart Van Assche [this message]
2025-07-14 17:25 ` Martin K. Petersen
2025-07-14 17:28 ` Bart Van Assche
2025-07-14 17:35 ` Martin K. Petersen
2025-07-07 21:02 ` [PATCH V2 2/3] scsi: ufs: core: Add ufshcd_dme_rmw to modify DME attributes Nitin Rawat
2025-07-07 21:09 ` Bart Van Assche
2025-07-08 7:59 ` Manivannan Sadhasivam
2025-07-07 21:03 ` [PATCH V2 3/3] scsi: ufs: qcom: Enable QUnipro Internal Clock Gating Nitin Rawat
2025-07-08 8:03 ` Manivannan Sadhasivam
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=5a1bd678-c935-4c1b-812d-a249f1caebb7@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=avri.altman@wdc.com \
--cc=ebiggers@google.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=neil.armstrong@linaro.org \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_nitirawa@quicinc.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).