From: Simon Horman <horms@kernel•org>
To: Rosen Penev <rosenp@gmail•com>
Cc: netdev@vger•kernel.org, Michael Ellerman <mpe@ellerman•id.au>,
Nicholas Piggin <npiggin@gmail•com>,
Christophe Leroy <christophe.leroy@csgroup•eu>,
Naveen N Rao <naveen@kernel•org>,
Madhavan Srinivasan <maddy@linux•ibm.com>,
Haren Myneni <haren@linux•ibm.com>,
Rick Lindsley <ricklind@linux•ibm.com>,
Nick Child <nnac123@linux•ibm.com>,
Thomas Falcon <tlfalcon@linux•ibm.com>,
Andrew Lunn <andrew+netdev@lunn•ch>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@lists•ozlabs.org>,
open list <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH net-next] ibmvnic: use ethtool string helpers
Date: Thu, 24 Oct 2024 16:13:24 +0100 [thread overview]
Message-ID: <20241024151324.GX1202098@kernel.org> (raw)
In-Reply-To: <20241022203240.391648-1-rosenp@gmail.com>
On Tue, Oct 22, 2024 at 01:32:40PM -0700, Rosen Penev wrote:
> They are the prefered way to copy ethtool strings.
>
> Avoids manually incrementing the data pointer.
>
> Signed-off-by: Rosen Penev <rosenp@gmail•com>
Reviewed-by: Simon Horman <horms@kernel•org>
next prev parent reply other threads:[~2024-10-24 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 20:32 [PATCH net-next] ibmvnic: use ethtool string helpers Rosen Penev
2024-10-23 18:58 ` Nick Child
2024-10-24 15:13 ` Simon Horman [this message]
2024-10-29 23:00 ` 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=20241024151324.GX1202098@kernel.org \
--to=horms@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=haren@linux$(echo .)ibm.com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maddy@linux$(echo .)ibm.com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=naveen@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nnac123@linux$(echo .)ibm.com \
--cc=npiggin@gmail$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=ricklind@linux$(echo .)ibm.com \
--cc=rosenp@gmail$(echo .)com \
--cc=tlfalcon@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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