From: Manivannan Sadhasivam <mani@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, stable@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Stanley Jhu <chu.stanley@gmail.com>,
Can Guo <quic_cang@quicinc.com>,
Asutosh Das <quic_asutoshd@quicinc.com>,
Bean Huo <beanhuo@micron.com>,
"Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
Arthur Simchaev <Arthur.Simchaev@wdc.com>
Subject: Re: [PATCH 1/2] scsi: ufs: Simplify power management during async scan
Date: Wed, 20 Dec 2023 22:29:05 +0530 [thread overview]
Message-ID: <20231220165905.GM3544@thinkpad> (raw)
In-Reply-To: <19c10384-8b08-4f9d-af74-7f09737b02a6@acm.org>
On Wed, Dec 20, 2023 at 08:36:28AM -0800, Bart Van Assche wrote:
> On 12/20/23 06:42, Manivannan Sadhasivam wrote:
> > On Mon, Dec 18, 2023 at 02:52:14PM -0800, Bart Van Assche wrote:
> > > ufshcd_init() calls pm_runtime_get_sync() before it calls
> > > async_schedule(). ufshcd_async_scan() calls pm_runtime_put_sync()
> > > directly or indirectly from ufshcd_add_lus(). Simplify
> > > ufshcd_async_scan() by always calling pm_runtime_put_sync() from
> > > ufshcd_async_scan().
> > >
> > > Cc: stable@vger.kernel.org
> >
> > No fixes tag?
>
> There is no Fixes: tag because this patch does not change the behavior of
> the UFS driver. The Cc: stable tag is present because the next patch in this
> series has a Fixes: tag and depends on this patch.
>
Ok.
- Mani
> Thanks,
>
> Bart.
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2023-12-20 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231218225229.2542156-1-bvanassche@acm.org>
2023-12-18 22:52 ` [PATCH 1/2] scsi: ufs: Simplify power management during async scan Bart Van Assche
2023-12-19 5:04 ` Can Guo
2023-12-20 14:42 ` Manivannan Sadhasivam
2023-12-20 16:36 ` Bart Van Assche
2023-12-20 16:59 ` Manivannan Sadhasivam [this message]
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=20231220165905.GM3544@thinkpad \
--to=mani@kernel.org \
--cc=Arthur.Simchaev@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=chu.stanley@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_asutoshd@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@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