netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	<netdev@vger.kernel.org>
Subject: [PATCH 0/1] pull request (net-next): ipsec-next 2023-07-19
Date: Wed, 19 Jul 2023 12:02:27 +0200	[thread overview]
Message-ID: <20230719100228.373055-1-steffen.klassert@secunet.com> (raw)

Just a leftover from the last development cycle:

1) delete a clear to zero of encap_oa, it is not needed anymore.
   From Leon Romanovsky.

Please pull or let me know if there are problems.

Thanks!

The following changes since commit b2cbac9b9b28730e9e53be20b6cdf979d3b9f27e:

  net: Remove low_thresh in ip defrag (2023-05-15 08:42:07 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git tags/ipsec-next-2023-07-19

for you to fetch changes up to a94fd40a18ae76ba76dbaa8eca0e3c46aa1142c1:

  xfrm: delete not-needed clear to zero of encap_oa (2023-06-09 09:19:11 +0200)

----------------------------------------------------------------
ipsec-next-2023-07-19

----------------------------------------------------------------
Leon Romanovsky (1):
      xfrm: delete not-needed clear to zero of encap_oa

 net/key/af_key.c | 1 -
 1 file changed, 1 deletion(-)

             reply	other threads:[~2023-07-19 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 10:02 Steffen Klassert [this message]
2023-07-19 10:02 ` [PATCH] xfrm: delete not-needed clear to zero of encap_oa Steffen Klassert
2023-07-20  3:50   ` patchwork-bot+netdevbpf

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=20230719100228.373055-1-steffen.klassert@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).