From: Joe Perches <joe@perches.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com
Subject: Re: [net-next v3 00/15][pull request] 100GbE Intel Wired LAN Driver Updates 2020-06-25
Date: Thu, 25 Jun 2020 20:37:10 -0700 [thread overview]
Message-ID: <8a6648981072dd69e1cdca3563d4b88d2b81ee93.camel@perches.com> (raw)
In-Reply-To: <20200626020737.775377-1-jeffrey.t.kirsher@intel.com>
On Thu, 2020-06-25 at 19:07 -0700, Jeff Kirsher wrote:
> This series introduces both the Intel Ethernet Common Module and the Intel
> Data Plane Function. The patches also incorporate extended features and
> functionality added in the virtchnl.h file.
Overall, perhaps the code wraps rather a lot more
at 80 columns than necessary.
It might be better reading if some of the code used
longer lines where reasonable.
next prev parent reply other threads:[~2020-06-26 3:37 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 2:07 [net-next v3 00/15][pull request] 100GbE Intel Wired LAN Driver Updates 2020-06-25 Jeff Kirsher
2020-06-26 2:07 ` [net-next v3 01/15] virtchnl: Extend AVF ops Jeff Kirsher
2020-06-26 2:07 ` [net-next v3 02/15] iecm: Add framework set of header files Jeff Kirsher
2020-06-26 2:07 ` [net-next v3 03/15] iecm: Add TX/RX " Jeff Kirsher
2020-06-26 2:07 ` [net-next v3 04/15] iecm: Common module introduction and function stubs Jeff Kirsher
2020-06-26 2:23 ` Joe Perches
2020-06-26 17:34 ` Brady, Alan
2020-06-26 17:43 ` Joe Perches
2020-06-26 2:07 ` [net-next v3 05/15] iecm: Add basic netdevice functionality Jeff Kirsher
2020-06-26 2:39 ` Joe Perches
2020-06-26 17:38 ` Brady, Alan
2020-06-26 2:07 ` [net-next v3 06/15] iecm: Implement mailbox functionality Jeff Kirsher
2020-06-26 2:57 ` Joe Perches
2020-06-26 17:44 ` Brady, Alan
2020-06-26 23:11 ` Joe Perches
2020-06-26 19:10 ` Jakub Kicinski
2020-06-29 18:51 ` Brady, Alan
2020-06-26 2:07 ` [net-next v3 07/15] iecm: Implement virtchnl commands Jeff Kirsher
2020-06-26 3:06 ` Joe Perches
2020-06-26 17:51 ` Brady, Alan
2020-06-26 2:07 ` [net-next v3 08/15] iecm: Implement vector allocation Jeff Kirsher
2020-06-26 2:07 ` [net-next v3 09/15] iecm: Init and allocate vport Jeff Kirsher
2020-06-26 19:00 ` Jakub Kicinski
2020-06-29 18:48 ` Brady, Alan
2020-06-26 2:07 ` [net-next v3 10/15] iecm: Deinit vport Jeff Kirsher
2020-06-26 2:07 ` [net-next v3 11/15] iecm: Add splitq TX/RX Jeff Kirsher
2020-06-26 19:58 ` Jakub Kicinski
2020-06-27 1:26 ` Joe Perches
2020-06-29 18:57 ` Brady, Alan
2020-06-26 2:07 ` [net-next v3 12/15] iecm: Add singleq TX/RX Jeff Kirsher
2020-06-26 3:12 ` Joe Perches
2020-06-26 17:52 ` Brady, Alan
2020-06-26 2:07 ` [net-next v3 13/15] iecm: Add ethtool Jeff Kirsher
2020-06-26 3:29 ` Joe Perches
2020-06-26 17:57 ` Brady, Alan
2020-06-26 18:57 ` Jakub Kicinski
2020-06-29 18:48 ` Brady, Alan
2020-06-26 19:14 ` Jakub Kicinski
2020-06-29 18:53 ` Brady, Alan
2020-06-26 19:27 ` Jakub Kicinski
2020-06-29 21:00 ` Brady, Alan
2020-06-29 21:31 ` Jakub Kicinski
2020-06-29 22:07 ` Brady, Alan
2020-06-26 19:29 ` Jakub Kicinski
2020-07-10 20:16 ` Brady, Alan
2020-06-26 2:07 ` [net-next v3 14/15] iecm: Add iecm to the kernel build system Jeff Kirsher
2020-06-26 3:32 ` Joe Perches
2020-06-29 18:46 ` Brady, Alan
2020-06-26 2:07 ` [net-next v3 15/15] idpf: Introduce idpf driver Jeff Kirsher
2020-06-26 3:35 ` Joe Perches
2020-06-29 18:47 ` Brady, Alan
2020-06-26 18:52 ` Jakub Kicinski
2020-06-30 23:48 ` Kirsher, Jeffrey T
2020-07-01 0:59 ` Jakub Kicinski
2020-07-01 1:13 ` Kirsher, Jeffrey T
2020-06-26 3:37 ` Joe Perches [this message]
2020-06-26 18:58 ` [net-next v3 00/15][pull request] 100GbE Intel Wired LAN Driver Updates 2020-06-25 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=8a6648981072dd69e1cdca3563d4b88d2b81ee93.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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.