From: Jakub Kicinski <kuba@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: David Miller <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH 0/5] pull request (net-next): ipsec-next 2022-07-20
Date: Mon, 25 Jul 2022 11:18:27 -0700 [thread overview]
Message-ID: <20220725111827.4aa36c4a@kernel.org> (raw)
In-Reply-To: <20220725122302.GI678471@gauss3.secunet.de>
On Mon, 25 Jul 2022 14:23:02 +0200 Steffen Klassert wrote:
> On Wed, Jul 20, 2022 at 10:17:41AM +0200, Steffen Klassert wrote:
> > 1) Don't set DST_NOPOLICY in IPv4, a recent patch made this
> > superfluous. From Eyal Birger.
> >
> > 2) Convert alg_key to flexible array member to avoid an iproute2
> > compile warning when built with gcc-12.
> > From Stephen Hemminger.
> >
> > 3) xfrm_register_km and xfrm_unregister_km do always return 0
> > so change the type to void. From Zhengchao Shao.
> >
> > 4) Fix spelling mistake in esp6.c
> > From Zhang Jiaming.
> >
> > 5) Improve the wording of comment above XFRM_OFFLOAD flags.
> > From Petr Vaněk.
> >
> > Please pull or let me know if there are problems.
>
> Can anyone reconsider this pull request?
>
> It is marked as Accepted in patchwork, but seems not to be included
> in net-next.
FTR DaveM pulled it this morning (e222dc8d8408 ("Merge branch 'master'
of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next"))
sorry for the wait!
prev parent reply other threads:[~2022-07-25 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 8:17 [PATCH 0/5] pull request (net-next): ipsec-next 2022-07-20 Steffen Klassert
2022-07-20 8:17 ` [PATCH 1/5] xfrm: no need to set DST_NOPOLICY in IPv4 Steffen Klassert
2022-07-20 8:17 ` [PATCH 2/5] xfrm: convert alg_key to flexible array member Steffen Klassert
2022-07-20 8:17 ` [PATCH 3/5] xfrm: change the type of xfrm_register_km and xfrm_unregister_km Steffen Klassert
2022-07-20 8:17 ` [PATCH 4/5] esp6: Fix spelling mistake Steffen Klassert
2022-07-20 8:17 ` [PATCH 5/5] xfrm: improve wording of comment above XFRM_OFFLOAD flags Steffen Klassert
2022-07-25 12:23 ` [PATCH 0/5] pull request (net-next): ipsec-next 2022-07-20 Steffen Klassert
2022-07-25 18:18 ` 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=20220725111827.4aa36c4a@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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.