public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Pawel Chmielewski <pawel.chmielewski@intel.com>
To: netdev@vger.kernel.org
Cc: intel-wired-lan@lists.osuosl.org, andrew@lunn.ch,
	aelior@marvell.com, manishc@marvell.com, horms@kernel.org,
	vladimir.oltean@nxp.com, pabeni@redhat.com, davem@davemloft.net,
	edumazet@google.com, jdamato@fastly.com,
	d-tatianin@yandex-team.ru, kuba@kernel.org,
	Pawel Chmielewski <pawel.chmielewski@intel.com>
Subject: [PATCH net-next v4 0/2] ethtool: Add link mode maps for forced speeds
Date: Wed, 11 Oct 2023 15:13:46 +0200	[thread overview]
Message-ID: <20231011131348.435353-1-pawel.chmielewski@intel.com> (raw)

The following patch set was initially a part of [1]. As the purpose of
the original series was to add the support of the new hardware to the
intel ice driver, the refactoring of advertised link modes mapping was
extracted to a new set.
The patch set adds a common mechanism for mapping Ethtool forced speeds
with Ethtool supported link modes, which can be used in drivers code.

[1] https://lore.kernel.org/netdev/20230823180633.2450617-1-pawel.chmielewski@intel.com

Changelog:
v3->v4:
Moved the macro for setting fields into the common header file

v2->v3:
Fixed whitespaces, added missing line at end of file

v1->v2:
Fixed formatting, typo, moved declaration of iterator to loop line.

Paul Greenwalt (1):
  ethtool: Add forced speed to supported link modes maps

Pawel Chmielewski (1):
  ice: Refactor finding advertised link speed

 drivers/net/ethernet/intel/ice/ice.h          |   1 +
 drivers/net/ethernet/intel/ice/ice_ethtool.c  | 193 ++++++++++++------
 drivers/net/ethernet/intel/ice/ice_main.c     |   2 +
 .../net/ethernet/qlogic/qede/qede_ethtool.c   |  46 ++---
 include/linux/ethtool.h                       |  27 +++
 net/ethtool/ioctl.c                           |  13 ++
 6 files changed, 183 insertions(+), 99 deletions(-)

-- 
2.37.3


             reply	other threads:[~2023-10-11 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 13:13 Pawel Chmielewski [this message]
2023-10-11 13:13 ` [PATCH net-next v4 1/2] ethtool: Add forced speed to supported link modes maps Pawel Chmielewski
2023-10-11 15:12   ` Jiri Pirko
2023-10-12 13:33     ` Pawel Chmielewski
2023-10-12 13:42       ` Jiri Pirko
2023-10-11 13:13 ` [PATCH net-next v4 2/2] ice: Refactor finding advertised link speed Pawel Chmielewski

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=20231011131348.435353-1-pawel.chmielewski@intel.com \
    --to=pawel.chmielewski@intel.com \
    --cc=aelior@marvell.com \
    --cc=andrew@lunn.ch \
    --cc=d-tatianin@yandex-team.ru \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jdamato@fastly.com \
    --cc=kuba@kernel.org \
    --cc=manishc@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vladimir.oltean@nxp.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