From: Bart Van Assche <bvanassche@acm.org>
To: "Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Stanley Chu <stanley.chu@mediatek.com>,
Avri Altman <avri.altman@wdc.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Asutosh Das <quic_asutoshd@quicinc.com>,
Bean Huo <beanhuo@micron.com>, Can Guo <quic_cang@quicinc.com>,
Arthur Simchaev <Arthur.Simchaev@wdc.com>
Subject: Re: [PATCH 4/5] scsi: ufs: core: Unexport ufshcd_hold() and ufshcd_release()
Date: Fri, 5 May 2023 12:00:28 -0700 [thread overview]
Message-ID: <01d01fa0-9a11-bdad-af82-b1ad9b07ad7b@acm.org> (raw)
In-Reply-To: <990e73a9-b42f-6d13-59a4-ac84edadd602@quicinc.com>
On 5/5/23 11:40, Bao D. Nguyen wrote:
> On 5/4/2023 4:50 PM, Bart Van Assche wrote:
>> Unexport these functions since these are only used by the UFS core.
>
> Qualcomm uses these ufshcd_hold() and ufshcd_release() functions in ufs-qcom.c. I am going to post Qualcomm's change soon.
Hi Bao,
I will drop this patch.
Does the code that you plan to post pass 'false' or 'true' as second
argument to ufshcd_hold()?
Thanks,
Bart.
next prev parent reply other threads:[~2023-05-05 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 23:50 [PATCH 0/5] ufs: Do not requeue while ungating the clock Bart Van Assche
2023-05-04 23:50 ` [PATCH 1/5] scsi: core: Rework scsi_host_block() Bart Van Assche
2023-05-05 15:44 ` Mike Christie
2023-05-04 23:50 ` [PATCH 2/5] scsi: core: Support setting BLK_MQ_F_BLOCKING Bart Van Assche
2023-05-05 15:44 ` Mike Christie
2023-05-04 23:50 ` [PATCH 3/5] scsi: ufs: Enable the BLK_MQ_F_BLOCKING flag Bart Van Assche
2023-05-04 23:50 ` [PATCH 4/5] scsi: ufs: core: Unexport ufshcd_hold() and ufshcd_release() Bart Van Assche
2023-05-05 18:40 ` Bao D. Nguyen
2023-05-05 19:00 ` Bart Van Assche [this message]
2023-05-07 5:20 ` Bao D. Nguyen
2023-05-04 23:50 ` [PATCH 5/5] scsi: ufs: Ungate the clock synchronously Bart Van Assche
2023-05-07 7:08 ` Avri Altman
2023-05-17 21:33 ` 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=01d01fa0-9a11-bdad-af82-b1ad9b07ad7b@acm.org \
--to=bvanassche@acm.org \
--cc=Arthur.Simchaev@wdc.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=jaegeuk@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_asutoshd@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=stanley.chu@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;
as well as URLs for NNTP newsgroup(s).