From: patchwork-bot+netdevbpf@kernel.org
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, justin.chen@broadcom.com,
florian.fainelli@broadcom.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, bcm-kernel-feedback-list@broadcom.com,
rafal@milecki.pl, opendmb@gmail.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 net-next] net: broadcom: use ethtool string helpers
Date: Thu, 07 Nov 2024 02:00:41 +0000 [thread overview]
Message-ID: <173094484124.1489169.8971635919773008705.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241104205317.306140-1-rosenp@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 4 Nov 2024 12:53:17 -0800 you wrote:
> The latter is the preferred way to copy ethtool strings.
>
> Avoids manually incrementing the pointer. Cleans up the code quite well.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> v2: split off bnx2x changes.
> .../ethernet/broadcom/asp2/bcmasp_ethtool.c | 6 +++---
> drivers/net/ethernet/broadcom/bcm63xx_enet.c | 12 +++++------
> drivers/net/ethernet/broadcom/bcmsysport.c | 20 +++++--------------
> drivers/net/ethernet/broadcom/bgmac.c | 3 +--
> .../net/ethernet/broadcom/genet/bcmgenet.c | 6 +++---
> drivers/net/phy/bcm-phy-lib.c | 3 +--
> 6 files changed, 19 insertions(+), 31 deletions(-)
Here is the summary with links:
- [PATCHv2,net-next] net: broadcom: use ethtool string helpers
https://git.kernel.org/netdev/net-next/c/fda960354eac
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-11-07 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 20:53 [PATCHv2 net-next] net: broadcom: use ethtool string helpers Rosen Penev
2024-11-04 22:26 ` Florian Fainelli
2024-11-07 2:00 ` 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=173094484124.1489169.8971635919773008705.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=justin.chen@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.com \
--cc=rafal@milecki.pl \
--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