From: Joe Damato <joe@dama.to>
To: Jon Kohler <jon@nutanix.com>
Cc: 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>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net-next] e1000e: ethtool: add get_channels support
Date: Mon, 4 May 2026 10:41:05 -0700 [thread overview]
Message-ID: <afjaMXktB3WmT7KC@devvm20253.cco0.facebook.com> (raw)
In-Reply-To: <20260504154823.2535612-1-jon@nutanix.com>
On Mon, May 04, 2026 at 08:48:23AM -0700, Jon Kohler wrote:
> e1000e hardware supports a single RX/TX queue pair, add basic support
> for ethtool -l (i.e. get_channels), so that callers indeed see a single
> queue.
>
> Signed-off-by: Jon Kohler <jon@nutanix.com>
> ---
> drivers/net/ethernet/intel/e1000e/ethtool.c | 26 +++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
Reviewed-by: Joe Damato <joe@dama.to>
WARNING: multiple messages have this Message-ID (diff)
From: Joe Damato <joe@dama.to>
To: Jon Kohler <jon@nutanix.com>
Cc: 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>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] e1000e: ethtool: add get_channels support
Date: Mon, 4 May 2026 10:41:05 -0700 [thread overview]
Message-ID: <afjaMXktB3WmT7KC@devvm20253.cco0.facebook.com> (raw)
In-Reply-To: <20260504154823.2535612-1-jon@nutanix.com>
On Mon, May 04, 2026 at 08:48:23AM -0700, Jon Kohler wrote:
> e1000e hardware supports a single RX/TX queue pair, add basic support
> for ethtool -l (i.e. get_channels), so that callers indeed see a single
> queue.
>
> Signed-off-by: Jon Kohler <jon@nutanix.com>
> ---
> drivers/net/ethernet/intel/e1000e/ethtool.c | 26 +++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
Reviewed-by: Joe Damato <joe@dama.to>
next prev parent reply other threads:[~2026-05-04 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 15:48 [Intel-wired-lan] [PATCH net-next] e1000e: ethtool: add get_channels support Jon Kohler
2026-05-04 15:48 ` Jon Kohler
2026-05-04 17:41 ` Joe Damato [this message]
2026-05-04 17:41 ` Joe Damato
2026-05-04 23:49 ` [Intel-wired-lan] " Jakub Kicinski
2026-05-04 23:49 ` Jakub Kicinski
2026-05-05 0:59 ` [Intel-wired-lan] " Jon Kohler
2026-05-05 0:59 ` Jon Kohler
2026-05-05 1:06 ` [Intel-wired-lan] " Jakub Kicinski
2026-05-05 1:06 ` Jakub Kicinski
2026-05-05 1:12 ` [Intel-wired-lan] " Jon Kohler
2026-05-05 1:12 ` Jon Kohler
2026-05-05 1:26 ` [Intel-wired-lan] " Jakub Kicinski
2026-05-05 1:26 ` Jakub Kicinski
2026-05-07 23:49 ` [Intel-wired-lan] " Jacob Keller
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=afjaMXktB3WmT7KC@devvm20253.cco0.facebook.com \
--to=joe@dama.to \
--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=jon@nutanix.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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.