From: Jakub Kicinski <kuba@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
intel-wired-lan@lists.osuosl.org (moderated list:INTEL ETHERNET
DRIVERS), linux-kernel@vger.kernel.org (open list)
Subject: Re: [Intel-wired-lan] [PATCHv4 net-next iwl-next] net: intel: use ethtool string helpers
Date: Fri, 6 Dec 2024 17:32:09 -0800 [thread overview]
Message-ID: <20241206173209.6f9fd5fe@kernel.org> (raw)
In-Reply-To: <20241207004737.33936-1-rosenp@gmail.com>
On Fri, 6 Dec 2024 16:47:37 -0800 Rosen Penev wrote:
> Cleans up the code quite well.
Maybe the ixgbevf changes, yes, but the rest of it is just churn.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
intel-wired-lan@lists.osuosl.org (moderated list:INTEL ETHERNET
DRIVERS), linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCHv4 net-next iwl-next] net: intel: use ethtool string helpers
Date: Fri, 6 Dec 2024 17:32:09 -0800 [thread overview]
Message-ID: <20241206173209.6f9fd5fe@kernel.org> (raw)
In-Reply-To: <20241207004737.33936-1-rosenp@gmail.com>
On Fri, 6 Dec 2024 16:47:37 -0800 Rosen Penev wrote:
> Cleans up the code quite well.
Maybe the ixgbevf changes, yes, but the rest of it is just churn.
next prev parent reply other threads:[~2024-12-07 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 0:47 [Intel-wired-lan] [PATCHv4 net-next iwl-next] net: intel: use ethtool string helpers Rosen Penev
2024-12-07 0:47 ` Rosen Penev
2024-12-07 1:32 ` Jakub Kicinski [this message]
2024-12-07 1:32 ` Jakub Kicinski
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=20241206173209.6f9fd5fe@kernel.org \
--to=kuba@kernel.org \
--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=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.