From: David Miller <davem@davemloft.net>
To: alobakin@marvell.com
Cc: kuba@kernel.org, irusskikh@marvell.com,
michal.kalderon@marvell.com, aelior@marvell.com,
denis.bolotin@marvell.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, andrew@lunn.ch,
GR-everest-linux-l2@marvell.com,
QLogic-Storage-Upstream@marvell.com, netdev@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 00/16] qed, qede: add support for new operating modes
Date: Mon, 20 Jul 2020 18:00:02 -0700 (PDT) [thread overview]
Message-ID: <20200720.180002.410400476834453177.davem@davemloft.net> (raw)
In-Reply-To: <20200720180815.107-1-alobakin@marvell.com>
From: Alexander Lobakin <alobakin@marvell.com>
Date: Mon, 20 Jul 2020 21:07:59 +0300
> This series covers the support for the following:
> - new port modes;
> - loopback modes, previously missing;
> - new speed/link modes;
> - several FEC modes;
> - multi-rate transceivers;
>
> and also cleans up and optimizes several related parts of code.
>
> v3 (from [2]):
> - dropped custom link mode declaration; qed, qede and qedf switched to
> Ethtool link modes and definitions (#0001, #0002, per Andrew Lunn's
> suggestion);
> - exchange more .text size to .initconst and .ro_after_init in qede
> (#0003).
>
> v2 (from [1]):
> - added a patch (#0010) that drops discussed dead struct member;
> - addressed checkpatch complaints on #0014 (former #0013);
> - rebased on top of latest net-next;
> - no other changes.
>
> [1] https://lore.kernel.org/netdev/20200716115446.994-1-alobakin@marvell.com/
> [2] https://lore.kernel.org/netdev/20200719201453.3648-1-alobakin@marvell.com/
Series applied, thank you.
prev parent reply other threads:[~2020-07-21 1:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 18:07 [PATCH v3 net-next 00/16] qed, qede: add support for new operating modes Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 01/16] linkmode: introduce linkmode_intersects() Alexander Lobakin
2020-07-20 18:31 ` Andrew Lunn
2020-07-20 18:08 ` [PATCH v3 net-next 02/16] qed, qede, qedf: convert link mode from u32 to ETHTOOL_LINK_MODE Alexander Lobakin
2020-07-20 18:34 ` Andrew Lunn
2020-07-20 18:08 ` [PATCH v3 net-next 03/16] qede: populate supported link modes maps on module init Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 04/16] qed: reformat public_port::transceiver_data a bit Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 05/16] qed: add support for multi-rate transceivers Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 06/16] qed: use transceiver data to fill link partner's advertising speeds Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 07/16] qed: reformat several structures a bit Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 08/16] qed: add support for Forward Error Correction Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 09/16] qede: format qede{,_vf}_ethtool_ops Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 10/16] qede: introduce support for FEC control Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 11/16] qed: reformat several structures a bit Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 12/16] qed: remove unused qed_hw_info::port_mode and QED_PORT_MODE Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 13/16] qed: add support for new port modes Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 14/16] qed: add missing loopback modes Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 15/16] qed: populate supported link modes maps on module init Alexander Lobakin
2020-07-20 18:08 ` [PATCH v3 net-next 16/16] qed: add support for the extended speed and FEC modes Alexander Lobakin
2020-07-21 0:14 ` [PATCH v3 net-next 00/16] qed, qede: add support for new operating modes Jakub Kicinski
2020-07-21 1:00 ` David Miller [this message]
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=20200720.180002.410400476834453177.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=GR-everest-linux-l2@marvell.com \
--cc=QLogic-Storage-Upstream@marvell.com \
--cc=aelior@marvell.com \
--cc=alobakin@marvell.com \
--cc=andrew@lunn.ch \
--cc=denis.bolotin@marvell.com \
--cc=irusskikh@marvell.com \
--cc=jejb@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michal.kalderon@marvell.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).