From: Sven Auhagen <sven.auhagen@voleatech.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
anthony.l.nguyen@intel.com, davem@davemloft.net,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
nhorman@redhat.com, sassmann@redhat.com,
sandeep.penigalapati@intel.com, brouer@redhat.com
Subject: Re: [PATCH v2 0/6] igb: xdp patches followup
Date: Mon, 19 Oct 2020 07:43:44 +0200 [thread overview]
Message-ID: <20201019054344.ei3yp2d7fqobgd6q@SvensMacBookAir-2.local> (raw)
In-Reply-To: <20201018120336.4a662b4a@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Sun, Oct 18, 2020 at 12:03:36PM -0700, Jakub Kicinski wrote:
> On Sun, 18 Oct 2020 15:39:51 +0200 Maciej Fijalkowski wrote:
> > - next time please specify the tree in the subject that you're targetting
> > this set to land; is it net or net-next? net-next is currently closed so
> > you probably would have to come back with this once it will be open
> > again
>
> Most of the patches here look like fixes, so we can take them into net
> but please repost them rather soon.
I will repost them today.
Best
Sven
next prev parent reply other threads:[~2020-10-19 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 7:12 [PATCH v2 0/6] igb: xdp patches followup sven.auhagen
2020-10-17 7:12 ` [PATCH v2 1/6] igb: XDP xmit back fix error code sven.auhagen
2020-10-17 7:12 ` [PATCH v2 2/6] igb: take vlan double header into account sven.auhagen
2020-10-17 7:12 ` [PATCH v2 3/6] igb: XDP extack message on error sven.auhagen
2020-10-17 7:12 ` [PATCH v2 4/6] igb: skb add metasize for xdp sven.auhagen
2020-10-17 7:12 ` [PATCH v2 5/6] igb: use xdp_do_flush sven.auhagen
2020-10-17 7:12 ` [PATCH v2 6/6] igb: avoid transmit queue timeout in xdp path sven.auhagen
2020-10-18 13:28 ` Maciej Fijalkowski
2020-10-18 13:39 ` [PATCH v2 0/6] igb: xdp patches followup Maciej Fijalkowski
2020-10-18 19:03 ` Jakub Kicinski
2020-10-19 5:43 ` Sven Auhagen [this message]
2020-10-19 5:43 ` Sven Auhagen
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=20201019054344.ei3yp2d7fqobgd6q@SvensMacBookAir-2.local \
--to=sven.auhagen@voleatech.de \
--cc=anthony.l.nguyen@intel.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sandeep.penigalapati@intel.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).