From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com
Subject: Re: [net-next 00/12][pull request] 40GbE Intel Wired LAN Driver Updates 2019-02-28
Date: Sun, 03 Mar 2019 13:00:17 -0800 (PST) [thread overview]
Message-ID: <20190303.130017.1521404116484398890.davem@davemloft.net> (raw)
In-Reply-To: <20190301050352.14978-1-jeffrey.t.kirsher@intel.com>
Please address the DPDK feedback...
prev parent reply other threads:[~2019-03-03 21:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 5:03 [net-next 00/12][pull request] 40GbE Intel Wired LAN Driver Updates 2019-02-28 Jeff Kirsher
2019-03-01 5:03 ` [net-next 01/12] i40e: Queues are reserved despite "Invalid argument" error Jeff Kirsher
2019-03-01 5:03 ` [net-next 02/12] i40e: Implement DDP support in i40e driver Jeff Kirsher
2019-03-01 19:19 ` Jakub Kicinski
2019-03-04 8:41 ` Loktionov, Aleksandr
2019-03-01 5:03 ` [net-next 03/12] i40e: don't allow changes to HW VLAN stripping on active port VLANs Jeff Kirsher
2019-03-01 5:03 ` [net-next 04/12] i40e: save PTP time before a device reset Jeff Kirsher
2019-03-01 5:03 ` [net-next 05/12] i40e: Fix for 10G ports LED not blinking Jeff Kirsher
2019-03-01 5:03 ` [net-next 06/12] i40e: Update i40e_init_dcb to return correct error Jeff Kirsher
2019-03-01 5:03 ` [net-next 07/12] i40e: Remove misleading messages for untrusted VF Jeff Kirsher
2019-03-01 5:03 ` [net-next 08/12] i40e: Changed maximum supported FW API version to 1.8 Jeff Kirsher
2019-03-01 5:03 ` [net-next 09/12] i40e: The driver now prints the API version in error message Jeff Kirsher
2019-03-01 5:03 ` [net-next 10/12] i40e: Report advertised link modes on 40GBASE_SR4 Jeff Kirsher
2019-03-01 5:03 ` [net-next 11/12] i40e: Able to add up to 16 MAC filters on an untrusted VF Jeff Kirsher
2019-03-01 5:03 ` [net-next 12/12] i40e: Fix misleading error message Jeff Kirsher
2019-03-03 21:00 ` David Miller [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=20190303.130017.1521404116484398890.davem@davemloft.net \
--to=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 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).