From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.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>,
"moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCHv3 net-next iwl-next] net: intel: use ethtool string helpers
Date: Wed, 4 Dec 2024 10:09:54 +0100 [thread overview]
Message-ID: <94ab7f28-c74b-49c5-920c-a3a881de0b86@intel.com> (raw)
In-Reply-To: <d97614cb-1798-46d2-a3b8-88fa100d9765@intel.com>
On 11/5/24 06:47, Przemek Kitszel wrote:
> On 10/31/24 22:14, Rosen Penev 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>
>> ---
>> v3: change custom get_strings to u8** to make sure pointer increments
>> get propagated.
>
> I'm sorry for misleading you here, or perhaps not being clear enough.
>
> Let me restate: I'm fine with double pointer, but single pointer is also
> fine, no need to change if not used.
>
> And my biggest corncern is that you change big chunks of the code for no
> reason, please either drop those changes/those drivers, or adjust to
> have only minimal changes.
>
> please fine this complain embedded in the code inline for ice, igb, igc,
> and ixgbe
I would be happy to accept your changes trimmed to the drivers I didn't
complained about, I find that part a valuable contribution from you
PS. No need to CC XDP/BFP list/people for such changes
[removed those]
>
>> v2: add iwl-next tag. use inline int in for loops.
>> .../net/ethernet/intel/e1000/e1000_ethtool.c | 10 ++---
>> drivers/net/ethernet/intel/e1000e/ethtool.c | 14 +++---
>> .../net/ethernet/intel/fm10k/fm10k_ethtool.c | 10 ++---
>> .../net/ethernet/intel/i40e/i40e_ethtool.c | 6 +--
>> drivers/net/ethernet/intel/ice/ice_ethtool.c | 43 +++++++++++--------
>> drivers/net/ethernet/intel/igb/igb_ethtool.c | 35 ++++++++-------
>> drivers/net/ethernet/intel/igbvf/ethtool.c | 10 ++---
>> drivers/net/ethernet/intel/igc/igc_ethtool.c | 36 ++++++++--------
>> .../net/ethernet/intel/ixgbe/ixgbe_ethtool.c | 32 +++++++-------
>> drivers/net/ethernet/intel/ixgbevf/ethtool.c | 36 ++++++----------
>> 10 files changed, 118 insertions(+), 114 deletions(-)
next prev parent reply other threads:[~2024-12-04 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 21:14 [Intel-wired-lan] [PATCHv3 net-next iwl-next] net: intel: use ethtool string helpers Rosen Penev
2024-11-05 5:47 ` Przemek Kitszel
2024-12-04 9:09 ` Przemek Kitszel [this message]
2024-12-07 0:49 ` Rosen Penev
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=94ab7f28-c74b-49c5-920c-a3a881de0b86@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--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