public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Veerasenareddy Burru <vburru@marvell.com>
Cc: davem@davemloft.net, kuba@kernel.org, corbet@lwn.net,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Abhijit Ayarekar <aayarekar@marvell.com>,
	Satananda Burla <sburla@marvell.com>
Subject: Re: [PATCH v3 1/7] octeon_ep: Add driver framework and device initialization
Date: Mon, 7 Mar 2022 14:56:43 +0200	[thread overview]
Message-ID: <YiYBC/AE0ltKNS9J@unreal> (raw)
In-Reply-To: <20220307092646.17156-2-vburru@marvell.com>

On Mon, Mar 07, 2022 at 01:26:40AM -0800, Veerasenareddy Burru wrote:
> Add driver framework and device setup and initialization for Octeon
> PCI Endpoint NIC.
> 
> Add implementation to load module, initilaize, register network device,
> cleanup and unload module.
> 
> Signed-off-by: Veerasenareddy Burru <vburru@marvell.com>
> Signed-off-by: Abhijit Ayarekar <aayarekar@marvell.com>
> Signed-off-by: Satananda Burla <sburla@marvell.com>
> ---
> V2 -> V3:
>   - fix the Title overline & underline mismatch in octeon_ep.rst,
>     reported by kernel test robot:
>     Reported-by: kernel test robot <lkp@intel.com>
> 
> V1 -> V2:
>   - split the patch into smaller patches.
>   - fix build errors observed with clang and "make W=1 C=1".
> 
>  .../device_drivers/ethernet/index.rst         |   1 +
>  .../ethernet/marvell/octeon_ep.rst            |  35 ++
>  MAINTAINERS                                   |   7 +
>  drivers/net/ethernet/marvell/Kconfig          |   1 +
>  drivers/net/ethernet/marvell/Makefile         |   1 +
>  .../net/ethernet/marvell/octeon_ep/Kconfig    |  20 +
>  .../net/ethernet/marvell/octeon_ep/Makefile   |   9 +
>  .../marvell/octeon_ep/octep_cn9k_pf.c         | 241 +++++++++
>  .../ethernet/marvell/octeon_ep/octep_config.h | 204 +++++++
>  .../marvell/octeon_ep/octep_ctrl_mbox.c       |  84 +++
>  .../marvell/octeon_ep/octep_ctrl_mbox.h       | 170 ++++++
>  .../marvell/octeon_ep/octep_ctrl_net.c        |  42 ++
>  .../marvell/octeon_ep/octep_ctrl_net.h        | 299 ++++++++++
>  .../ethernet/marvell/octeon_ep/octep_main.c   | 512 ++++++++++++++++++
>  .../ethernet/marvell/octeon_ep/octep_main.h   | 379 +++++++++++++
>  .../marvell/octeon_ep/octep_regs_cn9k_pf.h    | 367 +++++++++++++
>  .../net/ethernet/marvell/octeon_ep/octep_rx.c |  42 ++
>  .../net/ethernet/marvell/octeon_ep/octep_rx.h | 199 +++++++
>  .../net/ethernet/marvell/octeon_ep/octep_tx.c |  43 ++
>  .../net/ethernet/marvell/octeon_ep/octep_tx.h | 284 ++++++++++
>  20 files changed, 2940 insertions(+)
>  create mode 100644 Documentation/networking/device_drivers/ethernet/marvell/octeon_ep.rst
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/Kconfig
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/Makefile
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_cn9k_pf.c
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_config.h
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_ctrl_mbox.c
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_ctrl_mbox.h
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_ctrl_net.c
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_ctrl_net.h
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_main.c
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_main.h
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_regs_cn9k_pf.h
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_rx.c
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_rx.h
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_tx.c
>  create mode 100644 drivers/net/ethernet/marvell/octeon_ep/octep_tx.h

<...>

> +MODULE_AUTHOR("Veerasenareddy Burru <vburru@marvell.com>");
> +MODULE_DESCRIPTION(OCTEP_DRV_STRING);
> +MODULE_LICENSE("GPL");
> +MODULE_VERSION(OCTEP_DRV_VERSION_STR);

Please don't add driver versions to new drivers.

Thanks

  reply	other threads:[~2022-03-07 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  9:26 [PATCH v3 0/7] Add octeon_ep driver Veerasenareddy Burru
2022-03-07  9:26 ` [PATCH v3 1/7] octeon_ep: Add driver framework and device initialization Veerasenareddy Burru
2022-03-07 12:56   ` Leon Romanovsky [this message]
2022-03-07  9:26 ` [PATCH v3 2/7] octeon_ep: add hardware configuration APIs Veerasenareddy Burru
2022-03-07  9:26 ` [PATCH v3 3/7] octeon_ep: Add mailbox for control commands Veerasenareddy Burru
2022-03-07  9:26 ` [PATCH v3 4/7] octeon_ep: add Tx/Rx ring resource setup and cleanup Veerasenareddy Burru
2022-03-07  9:26 ` [PATCH v3 5/7] octeon_ep: add support for ndo ops Veerasenareddy Burru
2022-03-07  9:26 ` [PATCH v3 6/7] octeon_ep: add Tx/Rx processing and interrupt support Veerasenareddy Burru
2022-03-07  9:26 ` [PATCH v3 7/7] octeon_ep: add ethtool support for Octeon PCI Endpoint NIC Veerasenareddy Burru
2022-03-07 23:07 ` [PATCH v3 0/7] Add octeon_ep driver 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=YiYBC/AE0ltKNS9J@unreal \
    --to=leon@kernel.org \
    --cc=aayarekar@marvell.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sburla@marvell.com \
    --cc=vburru@marvell.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