All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: robh@kernel.org, saravanak@google.com, matthias.bgg@gmail.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew@lunn.ch,
	angelogioacchino.delregno@collabora.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	netdev@vger.kernel.org, geert+renesas@glider.be,
	prabhakar.mahadev-lad.rj@bp.renesas.com, biju.das.au@gmail.com,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/7] Add of_get_available_child_by_name()
Date: Fri, 07 Feb 2025 13:50:36 +0000	[thread overview]
Message-ID: <173893623629.2244005.12944730869712078303.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250205124235.53285-1-biju.das.jz@bp.renesas.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Wed,  5 Feb 2025 12:42:20 +0000 you wrote:
> There are lot of net 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.
> 
> v1->v2:
>  * Make it as a series as per [1] to cover the dependency.
>  * Added Rb tag from Rob for patch#1 and this patch can be merged through
>    net as it is the main user.
>  * Updated all the patches with patch suffix net-next
>  * Dropped _free() usage.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/7] of: base: Add of_get_available_child_by_name()
    https://git.kernel.org/netdev/net-next/c/8d3bbe4355ad
  - [net-next,v2,2/7] net: dsa: rzn1_a5psw: Use of_get_available_child_by_name()
    https://git.kernel.org/netdev/net-next/c/46df19a8dfdf
  - [net-next,v2,3/7] net: dsa: sja1105: Use of_get_available_child_by_name()
    https://git.kernel.org/netdev/net-next/c/a76568865c15
  - [net-next,v2,4/7] net: ethernet: mtk-star-emac: Use of_get_available_child_by_name()
    https://git.kernel.org/netdev/net-next/c/876e52b2d3f4
  - [net-next,v2,5/7] net: ethernet: mtk_eth_soc: Use of_get_available_child_by_name()
    https://git.kernel.org/netdev/net-next/c/1364004b5b91
  - [net-next,v2,6/7] net: ethernet: actions: Use of_get_available_child_by_name()
    https://git.kernel.org/netdev/net-next/c/76c82eb04332
  - [net-next,v2,7/7] net: ibm: emac: Use of_get_available_child_by_name()
    https://git.kernel.org/netdev/net-next/c/0584a917a209

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




      parent reply	other threads:[~2025-02-07 13:51 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
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 ` patchwork-bot+netdevbpf [this message]

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=173893623629.2244005.12944730869712078303.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@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.