From: Jakub Kicinski <kuba@kernel.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: davem@davemloft.net, Alan Brady <alan.brady@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
Alice Michael <alice.michael@intel.com>,
Phani Burra <phani.r.burra@intel.com>,
Joshua Hay <joshua.a.hay@intel.com>,
Madhu Chittim <madhu.chittim@intel.com>,
Pavan Kumar Linga <pavan.kumar.linga@intel.com>,
Donald Skidmore <donald.c.skidmore@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Sridhar Samudrala <sridhar.samudrala@intel.com>,
kbuild test robot <lkp@intel.com>
Subject: Re: [net-next v3 15/15] idpf: Introduce idpf driver
Date: Fri, 26 Jun 2020 11:52:36 -0700 [thread overview]
Message-ID: <20200626115236.7f36d379@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200626020737.775377-16-jeffrey.t.kirsher@intel.com>
On Thu, 25 Jun 2020 19:07:37 -0700 Jeff Kirsher wrote:
> +MODULE_AUTHOR("Intel Corporation, <linux.nics@intel.com>");
Corporations do not author things, people do. Please drop this.
next prev parent reply other threads:[~2020-06-26 18:52 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 [this message]
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 ` [net-next v3 00/15][pull request] 100GbE Intel Wired LAN Driver Updates 2020-06-25 Joe Perches
2020-06-26 18:58 ` 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=20200626115236.7f36d379@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=alan.brady@intel.com \
--cc=alice.michael@intel.com \
--cc=davem@davemloft.net \
--cc=donald.c.skidmore@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=joshua.a.hay@intel.com \
--cc=lkp@intel.com \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=pavan.kumar.linga@intel.com \
--cc=phani.r.burra@intel.com \
--cc=sassmann@redhat.com \
--cc=sridhar.samudrala@intel.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;
as well as URLs for NNTP newsgroup(s).