public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: "Michal Suchánek" <msuchanek@suse.de>,
	coxu@redhat.com, bhe@redhat.com, ebiederm@xmission.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] kexec: clean up arch_kexec_kernel_verify_sig" failed to apply to 5.15-stable tree
Date: Wed, 17 Aug 2022 14:06:39 +0200	[thread overview]
Message-ID: <YvzZz865jqWBEC7G@kroah.com> (raw)
In-Reply-To: <4b217b8801fe66a0fd71dad62571059d67f784bc.camel@linux.ibm.com>

On Mon, Aug 15, 2022 at 09:22:39AM -0400, Mimi Zohar wrote:
> On Mon, 2022-08-15 at 15:03 +0200, Greg KH wrote:
> > On Mon, Aug 15, 2022 at 02:41:25PM +0200, Michal Suchánek wrote:
> > > Hello,
> > > 
> > > it applies on top of 105e10e2cf1c
> > 
> > I see no such commit id in Linus's tree, what am I missing here?
> > 
> > confused,
> 
> 0738eceb6201 kexec: drop weak attribute from functions
> 65d9a9a60fd7 kexec_file: drop weak attribute from functions

That is 2 commit ids, not just one as Michal said, why?

I am totally confused here, sorry.  Can I have a list of the git ids
that need to be applied here, including the original git id of the patch
that started this whole thread off, so I know _EXACTLY_ what I need to
apply to the tree (and to what trees?)

thanks,

greg k-h

  reply	other threads:[~2022-08-17 12:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 11:48 FAILED: patch "[PATCH] kexec: clean up arch_kexec_kernel_verify_sig" failed to apply to 5.15-stable tree gregkh
2022-08-15 12:41 ` Michal Suchánek
2022-08-15 13:03   ` Greg KH
2022-08-15 13:22     ` Mimi Zohar
2022-08-17 12:06       ` Greg KH [this message]
2022-08-18  4:25         ` Coiby Xu
  -- strict thread matches above, loose matches on Subject: below --
2022-08-20 18:20 gregkh

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=YvzZz865jqWBEC7G@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bhe@redhat.com \
    --cc=coxu@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=msuchanek@suse.de \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox