All of lore.kernel.org
 help / color / mirror / Atom feed
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/11] pull request (net): ipsec 2023-08-15
Date: Wed, 16 Aug 2023 20:23:04 -0700	[thread overview]
Message-ID: <20230816202304.4a05369d@kernel.org> (raw)
In-Reply-To: <20230815095310.3310160-1-steffen.klassert@secunet.com>

On Tue, 15 Aug 2023 11:52:59 +0200 Steffen Klassert wrote:
> ipsec-2023-08-15

Looks merged, 5fc43ce03b in net, thanks!

      parent reply	other threads:[~2023-08-17  3:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15  9:52 [PATCH 0/11] pull request (net): ipsec 2023-08-15 Steffen Klassert
2023-08-15  9:53 ` [PATCH 01/11] net: xfrm: Fix xfrm_address_filter OOB read Steffen Klassert
2023-08-15  9:53 ` [PATCH 02/11] net: af_key: fix sadb_x_filter validation Steffen Klassert
2023-08-15  9:53 ` [PATCH 03/11] net: xfrm: Amend XFRMA_SEC_CTX nla_policy structure Steffen Klassert
2023-08-15  9:53 ` [PATCH 04/11] xfrm: Silence warnings triggerable by bad packets Steffen Klassert
2023-08-15  9:53 ` [PATCH 05/11] xfrm: fix slab-use-after-free in decode_session6 Steffen Klassert
2023-08-15  9:53 ` [PATCH 06/11] ip6_vti: " Steffen Klassert
2023-08-15  9:53 ` [PATCH 07/11] ip_vti: fix potential " Steffen Klassert
2023-08-15  9:53 ` [PATCH 08/11] xfrm: add NULL check in xfrm_update_ae_params Steffen Klassert
2023-08-15  9:53 ` [PATCH 09/11] xfrm: add forgotten nla_policy for XFRMA_MTIMER_THRESH Steffen Klassert
2023-08-15  9:53 ` [PATCH 10/11] xfrm: delete offloaded policy Steffen Klassert
2023-08-15  9:53 ` [PATCH 11/11] xfrm: don't skip free of empty state in acquire policy Steffen Klassert
2023-08-17  3:23 ` 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=20230816202304.4a05369d@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.