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: pull request (net): ipsec 2022-03-16
Date: Wed, 16 Mar 2022 11:44:38 -0700	[thread overview]
Message-ID: <20220316114438.11955749@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20220316121142.3142336-1-steffen.klassert@secunet.com>

On Wed, 16 Mar 2022 13:11:40 +0100 Steffen Klassert wrote:
> Two last fixes for this release cycle:
> 
> 1) Fix a kernel-info-leak in pfkey.
>    From Haimin Zhang.
> 
> 2) Fix an incorrect check of the return value of ipv6_skip_exthdr.
>    From Sabrina Dubroca.

Excellent, thank you!

> Please pull or let me know if there are problems.

One minor improvement to appease patchwork would be to add / keep the
[PATCH 0/n] prefix on the PR / cover letter when posting the patches
under it. It seems that patchwork is hopeless in delineating the
patches and the PR if that's not there. For whatever reason it grouped
the PR and patch 2 as a series and patch 1 was left separate :S

  parent reply	other threads:[~2022-03-16 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 12:11 pull request (net): ipsec 2022-03-16 Steffen Klassert
2022-03-16 12:11 ` [PATCH 1/2] af_key: add __GFP_ZERO flag for compose_sadb_supported in function pfkey_register Steffen Klassert
2022-03-16 18:50   ` patchwork-bot+netdevbpf
2022-03-16 12:11 ` [PATCH 2/2] esp6: fix check on ipv6_skip_exthdr's return value Steffen Klassert
2022-03-16 18:44 ` Jakub Kicinski [this message]
2022-03-19  7:49   ` pull request (net): ipsec 2022-03-16 Steffen Klassert
2022-03-19 19:05     ` Jakub Kicinski
2022-03-16 18: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=20220316114438.11955749@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --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.