Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next 00/19] Add iecm and idpf
Date: Fri,  4 Feb 2022 13:05:37 +0100	[thread overview]
Message-ID: <20220204120537.80979-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <20220128001009.721392-1-alan.brady@intel.com>

From: Alan Brady <alan.brady@intel.com>
Date: Thu, 27 Jan 2022 16:09:50 -0800

> This series introduces both the Intel Ethernet Common Module and the
> Intel Data Plane Function.  This also adds extended features and
> functionality to virtchnl with virtchnl_2.h.
>  
> The format of the series generally follows the flow of driver init to
> interface open. We go from probe into a hard reset followed by an init
> task. From there the rest of the netdev_ops and data path are added.
> Then lastly advanced features and idpf are introduced.
> 
> Currently this common layer (iecm) is initially only being used by only
> the idpf driver (PF driver for SmartNIC).  However, the plan is to
> eventually switch our iavf driver along with future drivers to use this
> common module.  The hope is to better enable code sharing going forward
> as well as support other developers writing drivers for our hardware

                                                                      ^

There's a dot '.' missing.

> 
> Alan Brady (17):
>   virtchnl: Add new virtchnl2 ops
>   iecm: add basic module init and documentation
>   iecm: add probe and remove
>   iecm: add api_init and controlq init
>   iecm: add vport alloc and virtchnl messages
>   iecm: add virtchnl messages for queues
>   iecm: finish virtchnl messages
>   iecm: add interrupts and configure netdev
>   iecm: alloc vport TX resources
>   iecm: alloc vport RX resources
>   iecm: add start_xmit and set_rx_mode
>   iecm: finish netdev_ops
>   iecm: implement splitq napi_poll
>   iecm: implement singleq napi_poll
>   iecm: implement ethtool callbacks
>   iecm: implement cloud filters
>   idpf: introduce idpf driver
> 
> Haiyue Wang (2):
>   iecm: implement flow director
>   iecm: add advanced rss

I'd like to remind here that you can *not* proceed with publishing
a v2 to netdev ML before at least me *and* Shannon (we're the only
two for now who did reviews here) say "I'm okay with your vN
revision".
I'm doing this because this is what you did previously, transferring
from our internal ML to IWL. In fact, you changed a bunch of code
and the authorship of two patches, but didn't publish a v2 there
and went directly here instead, without even providing a changelog,
so I only realized there were other changes apart from the authors
only when started comparing those two submissions.
Incorporating only the changes marked by you as "will fix" and not
getting the others resolved (places you didn't explain or answer to,
questionable "won't fix" which the reviewers disagree with etc.)
doesn't make this series ready for netdev ML.
And please supply changelogs at the end of the cover letter for each
subsequent revision, so people could easily see what was addressed
and what was not.

> 
>  .../device_drivers/ethernet/intel/idpf.rst    |   47 +
>  .../device_drivers/ethernet/intel/iecm.rst    |   93 +
>  MAINTAINERS                                   |    1 +
>  drivers/net/ethernet/intel/Kconfig            |   31 +
>  drivers/net/ethernet/intel/Makefile           |    2 +
>  drivers/net/ethernet/intel/idpf/Makefile      |   15 +
>  drivers/net/ethernet/intel/idpf/idpf_dev.h    |   17 +
>  drivers/net/ethernet/intel/idpf/idpf_devids.h |   10 +
>  drivers/net/ethernet/intel/idpf/idpf_main.c   |  140 +
>  drivers/net/ethernet/intel/idpf/idpf_reg.c    |  130 +
>  drivers/net/ethernet/intel/iecm/Makefile      |   21 +
>  .../net/ethernet/intel/iecm/iecm_controlq.c   |  649 ++
>  .../ethernet/intel/iecm/iecm_controlq_setup.c |  175 +
>  .../net/ethernet/intel/iecm/iecm_ethtool.c    | 1332 ++++
>  drivers/net/ethernet/intel/iecm/iecm_lib.c    | 5717 +++++++++++++++++
>  drivers/net/ethernet/intel/iecm/iecm_main.c   |   40 +
>  .../ethernet/intel/iecm/iecm_singleq_txrx.c   | 1229 ++++
>  drivers/net/ethernet/intel/iecm/iecm_txrx.c   | 4577 +++++++++++++
>  .../net/ethernet/intel/iecm/iecm_virtchnl.c   | 4240 ++++++++++++
>  drivers/net/ethernet/intel/include/iecm.h     |  973 +++
>  .../ethernet/intel/include/iecm_controlq.h    |  117 +
>  .../intel/include/iecm_controlq_api.h         |  185 +
>  .../ethernet/intel/include/iecm_lan_pf_regs.h |  131 +
>  .../ethernet/intel/include/iecm_lan_txrx.h    |  394 ++
>  drivers/net/ethernet/intel/include/iecm_mem.h |   20 +
>  .../net/ethernet/intel/include/iecm_txrx.h    |  733 +++
>  include/linux/avf/virtchnl.h                  | 1507 ++++-
>  include/linux/avf/virtchnl_2.h                | 1243 ++++
>  include/linux/avf/virtchnl_lan_desc.h         |  603 ++

--- 8< ---

> -- 
> 2.33.0

Thanks,
Al

      parent reply	other threads:[~2022-02-04 12:05 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  0:09 [Intel-wired-lan] [PATCH net-next 00/19] Add iecm and idpf Alan Brady
2022-01-28  0:09 ` [Intel-wired-lan] [PATCH net-next 01/19] virtchnl: Add new virtchnl2 ops Alan Brady
2022-02-02 22:13   ` Brady, Alan
2022-01-28  0:09 ` [Intel-wired-lan] [PATCH net-next 02/19] iecm: add basic module init and documentation Alan Brady
2022-01-28 11:56   ` Alexander Lobakin
2022-02-02 22:15     ` Brady, Alan
2022-02-01 19:44   ` Shannon Nelson
2022-02-03  3:08     ` Brady, Alan
2022-01-28  0:09 ` [Intel-wired-lan] [PATCH net-next 03/19] iecm: add probe and remove Alan Brady
2022-02-01 20:02   ` Shannon Nelson
2022-02-03  3:13     ` Brady, Alan
2022-01-28  0:09 ` [Intel-wired-lan] [PATCH net-next 04/19] iecm: add api_init and controlq init Alan Brady
2022-01-28 12:09   ` Alexander Lobakin
2022-02-02 22:16     ` Brady, Alan
2022-02-01 21:26   ` Shannon Nelson
2022-02-03  3:24     ` Brady, Alan
2022-02-03  3:40       ` Brady, Alan
2022-02-03  5:26         ` Shannon Nelson
2022-02-03 13:13       ` Alexander Lobakin
2022-01-28  0:09 ` [Intel-wired-lan] [PATCH net-next 05/19] iecm: add vport alloc and virtchnl messages Alan Brady
2022-01-28  4:19   ` kernel test robot
2022-01-28 12:39     ` Alexander Lobakin
2022-02-02 22:23       ` Brady, Alan
2022-01-28 12:32   ` Alexander Lobakin
2022-02-02 22:21     ` Brady, Alan
2022-02-03 13:23       ` Alexander Lobakin
2022-01-28  0:09 ` [Intel-wired-lan] [PATCH net-next 06/19] iecm: add virtchnl messages for queues Alan Brady
2022-01-28 13:03   ` Alexander Lobakin
2022-02-02 22:48     ` Brady, Alan
2022-02-03 10:08       ` Maciej Fijalkowski
2022-02-03 14:09       ` Alexander Lobakin
2022-01-28  0:09 ` [Intel-wired-lan] [PATCH net-next 07/19] iecm: finish virtchnl messages Alan Brady
2022-01-28 13:19   ` Alexander Lobakin
2022-02-02 23:06     ` Brady, Alan
2022-02-03 15:05       ` Alexander Lobakin
2022-02-03 15:16         ` Maciej Fijalkowski
2022-01-28  0:09 ` [Intel-wired-lan] [PATCH net-next 08/19] iecm: add interrupts and configure netdev Alan Brady
2022-01-28 13:34   ` Alexander Lobakin
2022-02-02 23:17     ` Brady, Alan
2022-02-03 15:55       ` Alexander Lobakin
2022-01-28  0:09 ` [Intel-wired-lan] [PATCH net-next 09/19] iecm: alloc vport TX resources Alan Brady
2022-02-02 23:45   ` Brady, Alan
2022-02-03 17:56     ` Alexander Lobakin
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 10/19] iecm: alloc vport RX resources Alan Brady
2022-01-28 14:16   ` Alexander Lobakin
2022-02-03  0:13     ` Brady, Alan
2022-02-03 18:29       ` Alexander Lobakin
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 11/19] iecm: add start_xmit and set_rx_mode Alan Brady
2022-01-28 16:35   ` Alexander Lobakin
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 12/19] iecm: finish netdev_ops Alan Brady
2022-01-28 17:06   ` Alexander Lobakin
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 13/19] iecm: implement splitq napi_poll Alan Brady
2022-01-28  5:21   ` kernel test robot
2022-01-28 17:44     ` Alexander Lobakin
2022-02-03  1:15       ` Brady, Alan
2022-01-28 17:38   ` Alexander Lobakin
2022-02-03  1:07     ` Brady, Alan
2022-02-04 11:50       ` Alexander Lobakin
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 14/19] iecm: implement singleq napi_poll Alan Brady
2022-01-28 17:57   ` Alexander Lobakin
2022-02-03  1:45     ` Brady, Alan
2022-02-03 19:05       ` Alexander Lobakin
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 15/19] iecm: implement ethtool callbacks Alan Brady
2022-01-28 18:13   ` Alexander Lobakin
2022-02-03  2:13     ` Brady, Alan
2022-02-03 19:54       ` Alexander Lobakin
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 16/19] iecm: implement flow director Alan Brady
2022-01-28 19:04   ` Alexander Lobakin
2022-02-03  2:41     ` Brady, Alan
2022-02-04 10:08       ` Alexander Lobakin
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 17/19] iecm: implement cloud filters Alan Brady
2022-01-28 19:38   ` Alexander Lobakin
2022-02-03  2:53     ` Brady, Alan
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 18/19] iecm: add advanced rss Alan Brady
2022-01-28 19:53   ` Alexander Lobakin
2022-02-03  2:55     ` Brady, Alan
2022-02-03 10:46       ` Maciej Fijalkowski
2022-02-04 10:22       ` Alexander Lobakin
2022-01-28  0:10 ` [Intel-wired-lan] [PATCH net-next 19/19] idpf: introduce idpf driver Alan Brady
2022-01-28 20:08   ` Alexander Lobakin
2022-02-03  3:07     ` Brady, Alan
2022-02-04 10:35       ` Alexander Lobakin
2022-02-04 12:05 ` Alexander Lobakin [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=20220204120537.80979-1-alexandr.lobakin@intel.com \
    --to=alexandr.lobakin@intel.com \
    --cc=intel-wired-lan@osuosl.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