From: Greg KH <gregkh@linuxfoundation.org>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: coxu@redhat.com, bhe@redhat.com, msuchanek@suse.de,
will@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] arm64: kexec_file: use more system keyrings to verify kernel" failed to apply to 5.19-stable tree
Date: Wed, 17 Aug 2022 14:02:44 +0200 [thread overview]
Message-ID: <YvzY5BOwFTkQd3IM@kroah.com> (raw)
In-Reply-To: <ebb3e67f78a8d7ab0e359517eadb3f39247a358f.camel@linux.ibm.com>
On Mon, Aug 15, 2022 at 02:11:44PM -0400, Mimi Zohar wrote:
> Hi Greg,
>
> On Mon, 2022-08-15 at 17:33 +0200, gregkh@linuxfoundation.org wrote:
> > The patch below does not apply to the 5.19-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> The commits contained in the 88b61b130334 ("Merge remote-tracking
> branch 'linux-integrity/kexec-keyrings' into next-integrity") should be
> applied in the proper order to avoid merge conflicts.
>
> The third patch has a dependency on the first two commits, which were
> initially in Andrew's tree. The third commit says, "Note later
> patches are dependent on this patch so it should be backported to the
> stable tree as well."
I need git commit ids of those commits please. Otherwise this is
impossible to determine given the huge number of commits in the tree.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-17 12:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 15:33 FAILED: patch "[PATCH] arm64: kexec_file: use more system keyrings to verify kernel" failed to apply to 5.19-stable tree gregkh
2022-08-15 18:11 ` Mimi Zohar
2022-08-17 12:02 ` Greg KH [this message]
2022-08-16 6:32 ` Coiby Xu
2022-08-16 7:59 ` Greg KH
2022-08-16 10:45 ` Coiby Xu
2022-08-16 13:14 ` Mimi Zohar
2022-08-17 10:22 ` Coiby Xu
2022-08-17 12:03 ` Greg KH
2022-08-17 12:11 ` Michal Suchánek
2022-08-17 12:16 ` Greg KH
2022-08-17 12:29 ` Michal Suchánek
2022-08-19 14:45 ` Greg KH
2022-08-18 3:44 ` Coiby Xu
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=YvzY5BOwFTkQd3IM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhe@redhat.com \
--cc=coxu@redhat.com \
--cc=msuchanek@suse.de \
--cc=stable@vger.kernel.org \
--cc=will@kernel.org \
--cc=zohar@linux.ibm.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.