From: Greg KH <gregkh@linuxfoundation.org>
To: Christophe LEROY <christophe.leroy@c-s.fr>
Cc: mpe@ellerman.id.au, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] powerpc/lib: fix book3s/32 boot failure due to code patching" failed to apply to 4.18-stable tree
Date: Thu, 11 Oct 2018 11:41:47 +0200 [thread overview]
Message-ID: <20181011094147.GA29184@kroah.com> (raw)
In-Reply-To: <cd6ef34f-6ca3-d97f-5e7f-30742403fdd4@c-s.fr>
On Thu, Oct 11, 2018 at 08:29:46AM +0200, Christophe LEROY wrote:
> Greg,
>
> You said in an previous email (below) that you had it queue for 4.18, was in
> a discution about the application of 51c3c62b58b3
>
> Are you trying to apply twice ?
No, I had not gotten to those older ones yet. I've now fixed this all
up. I think...
greg k-h
prev parent reply other threads:[~2018-10-11 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 6:16 FAILED: patch "[PATCH] powerpc/lib: fix book3s/32 boot failure due to code patching" failed to apply to 4.18-stable tree gregkh
2018-10-11 6:29 ` Christophe LEROY
2018-10-11 9:41 ` Greg KH [this message]
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=20181011094147.GA29184@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christophe.leroy@c-s.fr \
--cc=mpe@ellerman.id.au \
--cc=stable@vger.kernel.org \
/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