From: Steffen Klassert <steffen.klassert@secunet•com>
To: Nicolas Dichtel <nicolas.dichtel@6wind•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the ipsec tree
Date: Mon, 27 Sep 2021 13:18:33 +0200 [thread overview]
Message-ID: <20210927111833.GH1407957@gauss3.secunet.de> (raw)
In-Reply-To: <a3680eb9-44d0-efe9-7037-9799a66786f7@6wind.com>
On Mon, Sep 27, 2021 at 09:55:07AM +0200, Nicolas Dichtel wrote:
> Hi Stephen,
>
> Le 26/09/2021 à 22:49, Stephen Rothwell a écrit :
> > Hi all,
> >
> > In commit
> >
> > 93ec1320b017 ("xfrm: fix rcu lock in xfrm_notify_userpolicy()")
> >
> > Fixes tag
> >
> > Fixes: 703b94b93c19 ("xfrm: notify default policy on update")
> >
> > has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> > Maybe you meant
> >
> > Fixes: 88d0adb5f13b ("xfrm: notify default policy on update")
> >
> In fact, the sha1 comes from the ipsec tree, which is regularly rebased.
The testing branch of the ipsec tree might be rebased if I have
a bad commit there. The master branch of the ipsec tree will not
be rebased, as this branch is publicly used.
> The original patch is only in this tree for now.
> Steffen, maybe this fix could be squashed with the original commit?
As said, I never rebased the master branch so far and would only do
so in case of emergency.
next prev parent reply other threads:[~2021-09-27 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 20:49 linux-next: Fixes tag needs some work in the ipsec tree Stephen Rothwell
2021-09-27 7:55 ` Nicolas Dichtel
2021-09-27 11:18 ` Steffen Klassert [this message]
2021-09-27 12:37 ` Nicolas Dichtel
-- strict thread matches above, loose matches on Subject: below --
2020-04-20 10:57 Stephen Rothwell
2019-05-28 21:48 Stephen Rothwell
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=20210927111833.GH1407957@gauss3.secunet.de \
--to=steffen.klassert@secunet$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nicolas.dichtel@6wind$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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