From: Jakub Kicinski <kuba@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Leon Romanovsky <leon@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
<netdev@vger.kernel.org>, Bharat Bhushan <bbhushan2@marvell.com>
Subject: Re: [PATCH xfrm-next v9 0/8] Extend XFRM core to allow packet offload configuration
Date: Mon, 5 Dec 2022 16:09:14 -0800 [thread overview]
Message-ID: <20221205160914.37021a13@kernel.org> (raw)
In-Reply-To: <20221205092304.GC704954@gauss3.secunet.de>
On Mon, 5 Dec 2022 10:23:04 +0100 Steffen Klassert wrote:
> The two driver series and the core series would be about 40
> patches. If you are ok with taking such a last minute PR
> into net-next, we can go that way.
Fine by me.
prev parent reply other threads:[~2022-12-06 0:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 11:18 [PATCH xfrm-next v9 0/8] Extend XFRM core to allow packet offload configuration Leon Romanovsky
2022-11-27 11:18 ` [PATCH xfrm-next v9 1/8] xfrm: add new packet offload flag Leon Romanovsky
2022-11-27 11:18 ` [PATCH xfrm-next v9 2/8] xfrm: allow state packet offload mode Leon Romanovsky
2022-11-27 11:18 ` [PATCH xfrm-next v9 3/8] xfrm: add an interface to offload policy Leon Romanovsky
2022-11-27 11:18 ` [PATCH xfrm-next v9 4/8] xfrm: add TX datapath support for IPsec packet offload mode Leon Romanovsky
2022-12-02 9:30 ` Steffen Klassert
2022-12-02 17:59 ` Leon Romanovsky
2022-11-27 11:18 ` [PATCH xfrm-next v9 5/8] xfrm: add RX datapath protection " Leon Romanovsky
2022-11-27 11:18 ` [PATCH xfrm-next v9 6/8] xfrm: speed-up lookup of HW policies Leon Romanovsky
2022-11-27 11:18 ` [PATCH xfrm-next v9 7/8] xfrm: add support to HW update soft and hard limits Leon Romanovsky
2022-11-27 11:18 ` [PATCH xfrm-next v9 8/8] xfrm: document IPsec packet offload mode Leon Romanovsky
2022-12-02 9:42 ` [PATCH xfrm-next v9 0/8] Extend XFRM core to allow packet offload configuration Steffen Klassert
2022-12-02 18:05 ` Leon Romanovsky
2022-12-02 18:10 ` Jakub Kicinski
2022-12-02 18:31 ` Leon Romanovsky
2022-12-02 19:26 ` Jakub Kicinski
2022-12-02 19:45 ` Leon Romanovsky
2022-12-02 19:52 ` Jakub Kicinski
2022-12-05 9:23 ` Steffen Klassert
2022-12-06 0:09 ` Jakub Kicinski [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=20221205160914.37021a13@kernel.org \
--to=kuba@kernel.org \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.