From: Krzysztof Kozlowski <krzk@kernel.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drivers: soc: atmel: use automatic cleanup for device_node in atmel_soc_device_init()
Date: Thu, 31 Oct 2024 12:07:07 +0100 [thread overview]
Message-ID: <dfa83464-4632-45cf-a257-b9d9739d37e2@kernel.org> (raw)
In-Reply-To: <20241030-soc-atmel-soc-cleanup-v1-2-32b9e0773b14@gmail.com>
On 30/10/2024 18:10, Javier Carrasco wrote:
> Switch to a more robust approach to automatically release the node when
> it goes out of scope, dropping the need for explicit calls to
> of_node_put().
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
There is never a "drivers" prefix. Especially not first (because as
middle appears for FEW subsystems, not for SoC though).
>
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> ---
> drivers/soc/atmel/soc.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/soc/atmel/soc.c b/drivers/soc/atmel/soc.c
> index 64b1ad063073..298b542dd1c0 100644
> --- a/drivers/soc/atmel/soc.c
> +++ b/drivers/soc/atmel/soc.c
> @@ -399,15 +399,12 @@ static const struct of_device_id at91_soc_allowed_list[] __initconst = {
>
> static int __init atmel_soc_device_init(void)
> {
> - struct device_node *np = of_find_node_by_path("/");
> + struct device_node *np __free(device_node) = of_find_node_by_path("/");
>
> - if (!of_match_node(at91_soc_allowed_list, np)) {
> - of_node_put(np);
You just added this code. Don't add code which immediately you remove.
Squash two patches.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-31 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 17:10 [PATCH 0/2] drivers: soc: atmel: fix device_node release in atmel_soc_device_init() Javier Carrasco
2024-10-30 17:10 ` [PATCH 1/2] " Javier Carrasco
2024-10-30 17:10 ` [PATCH 2/2] drivers: soc: atmel: use automatic cleanup for device_node " Javier Carrasco
2024-10-31 11:07 ` Krzysztof Kozlowski [this message]
2024-10-31 11:14 ` Javier Carrasco
2024-10-31 11:17 ` Krzysztof Kozlowski
2024-10-31 12:27 ` Javier Carrasco
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=dfa83464-4632-45cf-a257-b9d9739d37e2@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=sudeep.holla@arm.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