From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Maramaina Naresh <quic_mnaresh@quicinc.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Peter Wang <peter.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
stanley.chu@mediatek.com
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
Stanley Jhu <chu.stanley@gmail.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, quic_cang@quicinc.com,
quic_nguyenb@quicinc.com
Subject: Re: [PATCH V4 2/2] ufs: ufs-mediatek: Enable CPU latency PM QoS support for MEDIATEK SoC
Date: Wed, 13 Dec 2023 11:59:55 +0100 [thread overview]
Message-ID: <84446493-2c3f-45b7-9d77-54a77e753d16@collabora.com> (raw)
In-Reply-To: <20231213103642.15320-3-quic_mnaresh@quicinc.com>
Il 13/12/23 11:36, Maramaina Naresh ha scritto:
> Revert the existing PM QoS feature from MEDIATEK UFS driver as similar
> PM QoS feature implementation is moved to core ufshcd.
>
> Signed-off-by: Maramaina Naresh <quic_mnaresh@quicinc.com>
IMO, title and description should say:
ufs: ufs-mediatek: Migrate to UFSHCD generic CPU latency PM QoS support
The PM QoS feature found in the MediaTek UFS driver was moved to the UFSHCD
core: remove it from here as it's now redundant.
with that fixed:
Reviewed-By: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
prev parent reply other threads:[~2023-12-13 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 10:36 [PATCH V4 0/2] Add CPU latency QoS support for ufs driver Maramaina Naresh
2023-12-13 10:36 ` [PATCH V4 1/2] ufs: core: " Maramaina Naresh
2023-12-13 10:59 ` AngeloGioacchino Del Regno
2023-12-13 10:36 ` [PATCH V4 2/2] ufs: ufs-mediatek: Enable CPU latency PM QoS support for MEDIATEK SoC Maramaina Naresh
2023-12-13 10:59 ` AngeloGioacchino Del Regno [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=84446493-2c3f-45b7-9d77-54a77e753d16@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=chu.stanley@gmail.com \
--cc=jejb@linux.ibm.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=peter.wang@mediatek.com \
--cc=quic_cang@quicinc.com \
--cc=quic_mnaresh@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
all inboxes | Powered by JetHome®