From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next PATCH 0/3] XDP for ixgbe
Date: Sun, 26 Feb 2017 17:35:47 -0800 [thread overview]
Message-ID: <1488159347.3553.31.camel@intel.com> (raw)
In-Reply-To: <58B1C101.7020704@gmail.com>
On Sat, 2017-02-25 at 09:38 -0800, John Fastabend wrote:
> There might need to be a couple versions to address feedback, but I
> assume you can put this on your dev_queue for whenever net-next
> opens?
Since Alex has some comments on patch 2 of the series, and Alex appears
to have some additional patches for igb/ixgbe coming, I will hold off
on this series.
I will monitor future versions, and will apply any future versions to
my dev-queue for testing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20170226/7b349e3b/attachment.asc>
next prev parent reply other threads:[~2017-02-27 1:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 17:32 [Intel-wired-lan] [net-next PATCH 0/3] XDP for ixgbe John Fastabend
2017-02-25 17:32 ` [Intel-wired-lan] [net-next PATCH 1/3] ixgbe: add XDP support for pass and drop actions John Fastabend
2017-02-25 18:18 ` kbuild test robot
2017-02-27 16:22 ` Alexander Duyck
2017-02-25 17:32 ` [Intel-wired-lan] [net-next PATCH 2/3] ixgbe: add support for XDP_TX action John Fastabend
2017-02-25 22:01 ` Alexander Duyck
2017-03-01 23:15 ` John Fastabend
2017-03-02 0:07 ` John Fastabend
2017-02-25 17:33 ` [Intel-wired-lan] [net-next PATCH 3/3] ixgbe: xdp support for adjust head John Fastabend
2017-02-27 16:32 ` Alexander Duyck
2017-03-02 0:23 ` John Fastabend
2017-02-25 17:38 ` [Intel-wired-lan] [net-next PATCH 0/3] XDP for ixgbe John Fastabend
2017-02-27 1:35 ` Jeff Kirsher [this message]
2017-02-25 18:58 ` Alexander Duyck
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=1488159347.3553.31.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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