From: Miquel Raynal <miquel.raynal@bootlin.com>
To: <shao.mingyin@zte.com.cn>
Cc: <jckuo@nvidia.com>, <vkoul@kernel.org>, <kishon@kernel.org>,
<linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<linux-tegra@vger.kernel.org>, <yang.yang29@zte.com.cn>,
<xu.xin16@zte.com.cn>, <ye.xingchen@zte.com.cn>,
<xie.ludan@zte.com.cn>
Subject: Re: [PATCH 1/2] phy: marvell: a3700-comphy: Use devm_platform_ioremap_resource_byname
Date: Tue, 01 Apr 2025 14:31:52 +0200 [thread overview]
Message-ID: <87cydwt64n.fsf@bootlin.com> (raw)
In-Reply-To: <20250401193836885cYSO33OlICvYYYmEMlB5J@zte.com.cn> (shao mingyin's message of "Tue, 1 Apr 2025 19:38:36 +0800 (CST)")
On 01/04/2025 at 19:38:36 +08, <shao.mingyin@zte.com.cn> wrote:
> From: Xie Ludan <xie.ludan@zte.com.cn>
>
> Introduce devm_platform_ioremap_resource_byname() to simplify resource
> retrieval and mapping.This new function consolidates
> platform_get_resource_byname() and devm_ioremap_resource() into
> a single call, improving code readability and reducing API call overhead.
>
> Signed-off-by: Xie Ludan <xie.ludan@zte.com.cn>
> Signed-off-by: Shao Mingyin <shao.mingyin@zte.com.cn>
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miquèl
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-04-01 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 11:31 [PATCH 0/2] Use devm_platform_ioremap_resource_byname in phy shao.mingyin
2025-04-01 11:38 ` [PATCH 1/2] phy: marvell: a3700-comphy: Use devm_platform_ioremap_resource_byname shao.mingyin
2025-04-01 12:31 ` Miquel Raynal [this message]
2025-04-11 11:20 ` Vinod Koul
2025-04-01 11:40 ` [PATCH 2/2] phy: tegra: xusb: " shao.mingyin
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=87cydwt64n.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=shao.mingyin@zte.com.cn \
--cc=thierry.reding@gmail.com \
--cc=vkoul@kernel.org \
--cc=xie.ludan@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=ye.xingchen@zte.com.cn \
/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).