From: Stephen Boyd <sboyd@kernel.org>
To: mturquette@baylibre.com, ye.xingchen@zte.com.cn
Cc: sugaya.taichi@socionext.com, orito.takao@socionext.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, chi.minghao@zte.com.cn
Subject: Re: [PATCH] clock: milbeaut: use devm_platform_get_and_ioremap_resource()
Date: Wed, 29 Mar 2023 14:48:09 -0700 [thread overview]
Message-ID: <b7a7d45026c2abe4dc7972eeac0fc3e3.sboyd@kernel.org> (raw)
In-Reply-To: <202211111439357842458@zte.com.cn>
Quoting ye.xingchen@zte.com.cn (2022-11-10 22:39:35)
> From: Minghao Chi <chi.minghao@zte.com.cn>
>
> Convert platform_get_resource(), devm_ioremap_resource() to a single
> call to devm_platform_get_and_ioremap_resource(), as this is exactly
> what this function does.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
> ---
Applied to clk-next
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: mturquette@baylibre.com, ye.xingchen@zte.com.cn
Cc: sugaya.taichi@socionext.com, orito.takao@socionext.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, chi.minghao@zte.com.cn
Subject: Re: [PATCH] clock: milbeaut: use devm_platform_get_and_ioremap_resource()
Date: Wed, 29 Mar 2023 14:48:09 -0700 [thread overview]
Message-ID: <b7a7d45026c2abe4dc7972eeac0fc3e3.sboyd@kernel.org> (raw)
In-Reply-To: <202211111439357842458@zte.com.cn>
Quoting ye.xingchen@zte.com.cn (2022-11-10 22:39:35)
> From: Minghao Chi <chi.minghao@zte.com.cn>
>
> Convert platform_get_resource(), devm_ioremap_resource() to a single
> call to devm_platform_get_and_ioremap_resource(), as this is exactly
> what this function does.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
> ---
Applied to clk-next
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-29 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 6:39 [PATCH] clock: milbeaut: use devm_platform_get_and_ioremap_resource() ye.xingchen
2022-11-11 6:39 ` ye.xingchen
2023-03-29 21:48 ` Stephen Boyd [this message]
2023-03-29 21:48 ` Stephen Boyd
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=b7a7d45026c2abe4dc7972eeac0fc3e3.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=chi.minghao@zte.com.cn \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=orito.takao@socionext.com \
--cc=sugaya.taichi@socionext.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.