From: David Daney <ddaney.cavm@gmail.com>
To: Raghu Vatsavayi <rvatsavayi@caviumnetworks.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 00/18] liquidio support for new device cn23xx
Date: Wed, 03 Aug 2016 13:51:46 -0700 [thread overview]
Message-ID: <57A25962.4030507@gmail.com> (raw)
In-Reply-To: <1470250549-10993-1-git-send-email-rvatsavayi@caviumnetworks.com>
On 08/03/2016 11:55 AM, Raghu Vatsavayi wrote:
> Dave,
>
> Please consider following patches for support of new device
> CN23XX in liquidio family of adapters. Patches may have to
> be applied in following order as some of the patches depend
> on earlier patches.
>
> Thanks
> Raghu Vatsavayi.
>
> Raghu Vatsavayi (18):
> 0001-liquidio-support-for-new-device-cn23xx.patch
> 0002-liquidio-support-for-new-device-cn23xx.patch
> 0003-liquidio-support-for-new-device-cn23xx.patch
> 0004-liquidio-support-for-new-device-cn23xx.patch
> 0005-liquidio-support-for-new-device-cn23xx.patch
> 0006-liquidio-support-for-new-device-cn23xx.patch
> 0007-liquidio-support-for-new-device-cn23xx.patch
> 0008-liquidio-support-for-new-device-cn23xx.patch
> 0009-liquidio-support-for-new-device-cn23xx.patch
> 0010-liquidio-support-for-new-device-cn23xx.patch
> 0011-liquidio-support-for-new-device-cn23xx.patch
> 0012-liquidio-support-for-new-device-cn23xx.patch
> 0013-liquidio-support-for-new-device-cn23xx.patch
> 0014-liquidio-support-for-new-device-cn23xx.patch
> 0015-liquidio-support-for-new-device-cn23xx.patch
> 0016-liquidio-support-for-new-device-cn23xx.patch
> 0017-liquidio-support-for-new-device-cn23xx.patch
> 0018-liquidio-support-for-new-device-cn23xx.patch
All 18 patches have identical subject lines, that is not correct.
Also each changelog begins with the identical text "This patch ...", we
know it is a patch, so saying that is redundant. Just say what the
patch does, something like "Add support for ..."
>
> drivers/net/ethernet/cavium/Kconfig | 4 +-
> drivers/net/ethernet/cavium/liquidio/Makefile | 24 +-
> .../ethernet/cavium/liquidio/cn23xx_pf_device.c | 1274 ++++++++++++++++++++
> .../ethernet/cavium/liquidio/cn23xx_pf_device.h | 63 +
> .../net/ethernet/cavium/liquidio/cn23xx_pf_regs.h | 602 +++++++++
> .../net/ethernet/cavium/liquidio/cn66xx_device.c | 12 +-
> .../net/ethernet/cavium/liquidio/cn66xx_device.h | 4 +-
> drivers/net/ethernet/cavium/liquidio/lio_core.c | 271 +++++
> drivers/net/ethernet/cavium/liquidio/lio_ethtool.c | 504 +++++++-
> drivers/net/ethernet/cavium/liquidio/lio_main.c | 1143 +++++++++++-------
> .../net/ethernet/cavium/liquidio/liquidio_common.h | 29 +-
> .../net/ethernet/cavium/liquidio/octeon_config.h | 59 +-
> .../net/ethernet/cavium/liquidio/octeon_console.c | 116 +-
> .../net/ethernet/cavium/liquidio/octeon_device.c | 352 ++++--
> .../net/ethernet/cavium/liquidio/octeon_device.h | 126 +-
> drivers/net/ethernet/cavium/liquidio/octeon_droq.c | 46 +-
> drivers/net/ethernet/cavium/liquidio/octeon_droq.h | 2 +
> drivers/net/ethernet/cavium/liquidio/octeon_iq.h | 2 +
> drivers/net/ethernet/cavium/liquidio/octeon_main.h | 32 +-
> .../net/ethernet/cavium/liquidio/octeon_mem_ops.c | 1 -
> .../net/ethernet/cavium/liquidio/octeon_network.h | 6 +-
> drivers/net/ethernet/cavium/liquidio/octeon_nic.c | 35 +-
> drivers/net/ethernet/cavium/liquidio/octeon_nic.h | 2 +-
> .../net/ethernet/cavium/liquidio/request_manager.c | 170 ++-
> .../ethernet/cavium/liquidio/response_manager.c | 9 +-
> 25 files changed, 4199 insertions(+), 689 deletions(-)
> create mode 100644 drivers/net/ethernet/cavium/liquidio/cn23xx_pf_device.c
> create mode 100644 drivers/net/ethernet/cavium/liquidio/cn23xx_pf_device.h
> create mode 100644 drivers/net/ethernet/cavium/liquidio/cn23xx_pf_regs.h
> create mode 100644 drivers/net/ethernet/cavium/liquidio/lio_core.c
>
next prev parent reply other threads:[~2016-08-03 20:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 18:55 [PATCH net-next 00/18] liquidio support for new device cn23xx Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 01/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 02/18] " Raghu Vatsavayi
2016-08-04 18:12 ` Yuval Mintz
2016-08-03 18:55 ` [PATCH net-next 03/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 04/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 05/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 06/18] " Raghu Vatsavayi
2016-08-04 0:13 ` kbuild test robot
2016-08-03 18:55 ` [PATCH net-next 07/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 08/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 09/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 10/18] " Raghu Vatsavayi
2016-08-04 17:07 ` Yuval Mintz
2016-08-03 18:55 ` [PATCH net-next 11/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 12/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 13/18] " Raghu Vatsavayi
2016-08-04 16:04 ` Yuval Mintz
2016-08-03 18:55 ` [PATCH net-next 14/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 15/18] " Raghu Vatsavayi
2016-08-03 22:54 ` kbuild test robot
2016-08-03 23:15 ` kbuild test robot
2016-08-03 18:55 ` [PATCH net-next 16/18] " Raghu Vatsavayi
2016-08-04 5:58 ` kbuild test robot
2016-08-03 18:55 ` [PATCH net-next 17/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 18/18] " Raghu Vatsavayi
2016-08-03 20:51 ` David Daney [this message]
2016-08-03 22:05 ` [PATCH net-next 00/18] " David Miller
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=57A25962.4030507@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rvatsavayi@caviumnetworks.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.