public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, michael.hennerich@analog.com,
	andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrei.botila@oss.nxp.com,
	ansuelsmth@gmail.com, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: use ethtool string helpers
Date: Sun, 03 Nov 2024 19:20:31 +0000	[thread overview]
Message-ID: <173066163149.3236514.2076673237259299128.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241029234641.11448-1-rosenp@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 29 Oct 2024 16:46:41 -0700 you wrote:
> These are the preferred way to copy ethtool strings.
> 
> Avoids incrementing pointers all over the place.
> 
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
>  drivers/net/phy/adin.c            |  6 ++----
>  drivers/net/phy/icplus.c          |  3 +--
>  drivers/net/phy/marvell.c         | 12 ++++--------
>  drivers/net/phy/micrel.c          |  6 ++----
>  drivers/net/phy/mscc/mscc_main.c  |  3 +--
>  drivers/net/phy/nxp-c45-tja11xx.c |  6 ++----
>  drivers/net/phy/nxp-cbtx.c        |  2 +-
>  drivers/net/phy/qcom/qca83xx.c    |  6 ++----
>  8 files changed, 15 insertions(+), 29 deletions(-)

Here is the summary with links:
  - [net-next] net: phy: use ethtool string helpers
    https://git.kernel.org/netdev/net-next/c/1441df3a37ec

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



      reply	other threads:[~2024-11-03 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 23:46 [PATCH net-next] net: phy: use ethtool string helpers Rosen Penev
2024-11-03 19:20 ` 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=173066163149.3236514.2076673237259299128.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrei.botila@oss.nxp.com \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael.hennerich@analog.com \
    --cc=netdev@vger.kernel.org \
    --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