All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Yannik Sembritzki <yannik@sembritzki.me>
Cc: dhowells@redhat.com, torvalds@linux-foundation.org,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] Fix kexec forbidding kernels signed with keys in the" failed to apply to 4.9-stable tree
Date: Fri, 7 Sep 2018 12:53:30 +0200	[thread overview]
Message-ID: <20180907105330.GA13726@kroah.com> (raw)
In-Reply-To: <09e21ad6-8808-7de4-c99d-b6b2cfe205c9@sembritzki.me>

On Fri, Sep 07, 2018 at 12:34:08PM +0200, Yannik Sembritzki wrote:
> This patch applies cleanly for me on the linux-4.9.y branch. Could you
> tell me what the problem is here?

The dependant patch fails to apply, so this one fails to build, sorry
for not being more obviuos about this.

So a backport of both is needed here.

thanks,

greg k-h

  reply	other threads:[~2018-09-07 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07  9:14 FAILED: patch "[PATCH] Fix kexec forbidding kernels signed with keys in the" failed to apply to 4.9-stable tree gregkh
2018-09-07 10:34 ` Yannik Sembritzki
2018-09-07 10:53   ` Greg KH [this message]
2018-09-07 10:56     ` Yannik Sembritzki
2018-09-07 11:01       ` Greg KH
2018-09-07 11:19         ` [PATCH 1/2] Replace the use of a magic number that indicates that verify_*_signature() should use the secondary keyring with a symbol Yannik Sembritzki
2018-09-07 11:19         ` [PATCH 2/2] The split of .system_keyring into .builtin_trusted_keys and .secondary_trusted_keys broke kexec, thereby preventing kernels signed by keys which are now in the secondary keyring from being kexec'd Yannik Sembritzki

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=20180907105330.GA13726@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dhowells@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yannik@sembritzki.me \
    /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.