From: patchwork-bot+netdevbpf@kernel.org
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org, o.rempel@pengutronix.de
Subject: Re: [PATCH net-next v2 0/3] use more devm for ag71xx
Date: Fri, 16 Aug 2024 18:30:30 +0000 [thread overview]
Message-ID: <172383303025.3598282.2567158642009588521.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240813170516.7301-1-rosenp@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 13 Aug 2024 10:04:56 -0700 you wrote:
> Some of these were introduced after the driver got introduced. In any
> case, using more devm allows removal of the remove function and overall
> simplifies the code. All of these were tested on a TP-LINK Archer C7v2.
>
> Rosen Penev (3):
> net: ag71xx: devm_clk_get_enabled
> net: ag71xx: use devm for of_mdiobus_register
> net: ag71xx: use devm for register_netdev
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] net: ag71xx: devm_clk_get_enabled
https://git.kernel.org/netdev/net-next/c/df37fcf58f2a
- [net-next,v2,2/3] net: ag71xx: use devm for of_mdiobus_register
https://git.kernel.org/netdev/net-next/c/8ef34bea8cad
- [net-next,v2,3/3] net: ag71xx: use devm for register_netdev
https://git.kernel.org/netdev/net-next/c/cc20a4791641
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-08-16 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 17:04 [PATCH net-next v2 0/3] use more devm for ag71xx Rosen Penev
2024-08-13 17:04 ` [PATCH net-next v2 1/3] net: ag71xx: devm_clk_get_enabled Rosen Penev
2024-08-13 17:04 ` [PATCH net-next v2 2/3] net: ag71xx: use devm for of_mdiobus_register Rosen Penev
2024-08-13 17:04 ` [PATCH net-next v2 3/3] net: ag71xx: use devm for register_netdev Rosen Penev
2024-08-16 18:30 ` 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=172383303025.3598282.2567158642009588521.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=rosenp@gmail.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;
as well as URLs for NNTP newsgroup(s).