From: David Miller <davem@davemloft.net>
To: jarod@redhat.com
Cc: linux-kernel@vger.kernel.org, j.vosburgh@gmail.com,
vfalico@gmail.com, andy@greyhouse.net,
jeffrey.t.kirsher@intel.com, kuba@kernel.org,
steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH net-next 1/4] xfrm: bail early on slave pass over skb
Date: Mon, 08 Jun 2020 19:03:51 -0700 (PDT) [thread overview]
Message-ID: <20200608.190351.685181495758257506.davem@davemloft.net> (raw)
In-Reply-To: <20200608210058.37352-2-jarod@redhat.com>
net-next is closed, thank you
next prev parent reply other threads:[~2020-06-09 2:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 21:00 [PATCH net-next 0/4] bonding: initial support for hardware crypto offload Jarod Wilson
2020-06-08 21:00 ` [PATCH net-next 1/4] xfrm: bail early on slave pass over skb Jarod Wilson
2020-06-09 2:03 ` David Miller [this message]
2020-06-08 21:00 ` [PATCH net-next 2/4] ixgbe_ipsec: become aware of when running as a bonding slave Jarod Wilson
2020-06-08 23:19 ` Kirsher, Jeffrey T
2020-06-08 21:00 ` [PATCH net-next 3/4] bonding: support hardware encryption offload to slaves Jarod Wilson
2020-06-08 23:48 ` Jay Vosburgh
2020-06-09 0:14 ` Jarod Wilson
2020-06-08 21:00 ` [PATCH net-next 4/4] mlx5: become aware of when running as a bonding slave Jarod Wilson
2020-06-10 18:59 ` [PATCH net-next v2 0/4] bonding: initial support for hardware crypto offload Jarod Wilson
2020-06-10 18:59 ` [PATCH net-next v2 1/4] xfrm: bail early on slave pass over skb Jarod Wilson
2020-06-10 18:59 ` [PATCH net-next v2 2/4] ixgbe_ipsec: become aware of when running as a bonding slave Jarod Wilson
2020-06-10 18:59 ` [PATCH net-next v2 3/4] mlx5: " Jarod Wilson
2020-06-11 21:51 ` Saeed Mahameed
2020-06-21 20:25 ` Jarod Wilson
2020-06-23 19:57 ` Saeed Mahameed
2020-06-10 18:59 ` [PATCH net-next v2 4/4] bonding: support hardware encryption offload to slaves Jarod Wilson
2020-06-19 10:26 ` [PATCH net-next v2 0/4] bonding: initial support for hardware crypto offload Jeff Kirsher
2020-06-19 14:26 ` Jarod Wilson
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=20200608.190351.685181495758257506.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=herbert@gondor.apana.org.au \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=j.vosburgh@gmail.com \
--cc=jarod@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=vfalico@gmail.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).