From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Friday Yang <friday.yang@mediatek.com>
Cc: Yong Wu <yong.wu@mediatek.com>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v6 3/3] memory: mtk-smi: mt8188: Use devm_pm_runtime_enable
Date: Wed, 9 Apr 2025 10:26:18 +0200 [thread overview]
Message-ID: <e777f95c-c21f-4a91-b044-5fc19eb22c3d@collabora.com> (raw)
In-Reply-To: <20250408-woodoo-quick-worm-bf82b4@shite>
Il 08/04/25 08:29, Krzysztof Kozlowski ha scritto:
> On Tue, Apr 08, 2025 at 11:31:56AM GMT, Friday Yang wrote:
>> Replace pm_runtime_enable with the devres-enabled version which
>> can trigger pm_runtime_disable.
>>
>> Signed-off-by: Friday Yang <friday.yang@mediatek.com>
>> ---
>> drivers/memory/mtk-smi.c | 16 +++++++++-------
>> 1 file changed, 9 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/memory/mtk-smi.c b/drivers/memory/mtk-smi.c
>> index f25d46d2ef33..daef6d350419 100644
>> --- a/drivers/memory/mtk-smi.c
>> +++ b/drivers/memory/mtk-smi.c
>> @@ -713,16 +713,17 @@ static int mtk_smi_larb_probe(struct platform_device *pdev)
>> if (ret)
>> goto err_link_remove;
>>
>> - pm_runtime_enable(dev);
>> + ret = devm_pm_runtime_enable(dev);
>> + if (ret)
>> + goto err_link_remove;
>> +
>> platform_set_drvdata(pdev, larb);
>> ret = component_add(dev, &mtk_smi_larb_component_ops);
>> if (ret)
>> - goto err_pm_disable;
>> + goto err_link_remove;
>>
>> return 0;
>>
>> -err_pm_disable:
>> - pm_runtime_disable(dev);
>
> You now broke/changed the order of cleanup without any explanation.
>
> Best regards,
> Krzysztof
>
I agree some comment in the commit description saying that the cleanup reordering
doesn't matter in this specific case would've been nice to have, but anyway IMO
it's not a big deal - he didn't break anything, anyway :-)
Instead, the big deal is that Friday forgot to retain Reviewed-by and Acked-by tags
that were released to him on those patches....... :-)
Cheers,
Angelo
next prev parent reply other threads:[~2025-04-09 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 3:31 [PATCH v6 0/3] Add SMI reset and clamp for MediaTek MT8188 SoC Friday Yang
2025-04-08 3:31 ` [PATCH v6 1/3] dt-bindings: memory: mediatek: Add SMI reset and clamp for MT8188 Friday Yang
2025-04-08 6:27 ` Krzysztof Kozlowski
2025-04-08 3:31 ` [PATCH v6 2/3] memory: mtk-smi: mt8188: " Friday Yang
2025-04-08 3:31 ` [PATCH v6 3/3] memory: mtk-smi: mt8188: Use devm_pm_runtime_enable Friday Yang
2025-04-08 6:29 ` Krzysztof Kozlowski
2025-04-09 8:26 ` AngeloGioacchino Del Regno [this message]
2025-04-09 9:56 ` Krzysztof Kozlowski
2025-04-09 15:50 ` AngeloGioacchino Del Regno
2025-04-09 16:13 ` Krzysztof Kozlowski
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=e777f95c-c21f-4a91-b044-5fc19eb22c3d@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=friday.yang@mediatek.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=yong.wu@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