From: Simon Horman <horms@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew@lunn.ch>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
netdev@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.au@gmail.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/7] of: base: Add of_get_available_child_by_name()
Date: Fri, 7 Feb 2025 09:45:32 +0000 [thread overview]
Message-ID: <20250207094532.GC554665@kernel.org> (raw)
In-Reply-To: <20250205124235.53285-2-biju.das.jz@bp.renesas.com>
On Wed, Feb 05, 2025 at 12:42:21PM +0000, Biju Das wrote:
> There are lot of drivers using of_get_child_by_name() followed by
> of_device_is_available() to find the available child node by name for a
> given parent. Provide a helper for these users to simplify the code.
>
> Suggested-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> previous v2->v2
> * Added Rb tag from Rob.
> v1->previous v2:
> * Updated commit description.
> * Updated kerneldoc comment block
> * Avoided code duplication by using of_get_child_by_name().
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-02-07 9:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 12:42 [PATCH net-next v2 0/7] Add of_get_available_child_by_name() Biju Das
2025-02-05 12:42 ` [PATCH net-next v2 1/7] of: base: " Biju Das
2025-02-07 9:45 ` Simon Horman [this message]
2025-02-05 12:42 ` [PATCH net-next v2 2/7] net: dsa: rzn1_a5psw: Use of_get_available_child_by_name() Biju Das
2025-02-07 9:47 ` Simon Horman
2025-02-07 17:41 ` Vladimir Oltean
2025-02-05 12:42 ` [PATCH net-next v2 3/7] net: dsa: sja1105: " Biju Das
2025-02-07 9:47 ` Simon Horman
2025-02-07 17:43 ` Vladimir Oltean
2025-02-05 12:42 ` [PATCH net-next v2 4/7] net: ethernet: mtk-star-emac: " Biju Das
2025-02-07 9:51 ` Simon Horman
2025-02-05 12:42 ` [PATCH net-next v2 5/7] net: ethernet: mtk_eth_soc: " Biju Das
2025-02-07 9:52 ` Simon Horman
2025-02-05 12:42 ` [PATCH net-next v2 6/7] net: ethernet: actions: " Biju Das
2025-02-07 9:53 ` Simon Horman
2025-02-05 12:42 ` [PATCH net-next v2 7/7] net: ibm: emac: " Biju Das
2025-02-07 9:53 ` Simon Horman
2025-02-07 13:50 ` [PATCH net-next v2 0/7] Add of_get_available_child_by_name() patchwork-bot+netdevbpf
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=20250207094532.GC554665@kernel.org \
--to=horms@kernel.org \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=saravanak@google.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 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.