From: Greg KH <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Chen Jingwen <chenjingwen6@huawei.com>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH] [Rebased for 5.4] powerpc/kasan: Fix early region not updated correctly
Date: Sun, 3 Apr 2022 14:26:34 +0200 [thread overview]
Message-ID: <YkmSeqRUjqbH9dcX@kroah.com> (raw)
In-Reply-To: <fd2c0d7a-e194-1ce4-4a5f-2d66ae0d350a@csgroup.eu>
On Sun, Apr 03, 2022 at 11:54:55AM +0000, Christophe Leroy wrote:
>
>
> Le 03/04/2022 à 12:25, Greg KH a écrit :
> > On Sat, Apr 02, 2022 at 06:13:31PM +0200, Christophe Leroy wrote:
> >> From: Chen Jingwen <chenjingwen6@huawei.com>
> >>
> >> This is backport for 5.4
> >>
> >> Upstream commit 5647a94a26e352beed61788b46e035d9d12664cd
> >
> > This is not a commit in Linus's tree :(
> >
>
> Oops. Don't know what I did, that's indeed the commit after I
> cherry-picked it on top of 5.4.188 and before I modified it.
>
> According to the mail you sent me yesterday to tell it FAILED to apply
> on 5.4, the upstream commit is dd75080aa8409ce10d50fb58981c6b59bf8707d3
Can you resend with this fixed up please?
thanks,
greg k-h
next prev parent reply other threads:[~2022-04-03 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 16:13 [PATCH] [Rebased for 5.4] powerpc/kasan: Fix early region not updated correctly Christophe Leroy
2022-04-03 10:25 ` Greg KH
2022-04-03 11:54 ` Christophe Leroy
2022-04-03 12:26 ` Greg KH [this message]
2022-04-12 2:17 ` ChenJingwen
-- strict thread matches above, loose matches on Subject: below --
2022-04-03 13:49 Christophe Leroy
2022-04-04 7:49 ` Greg KH
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=YkmSeqRUjqbH9dcX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chenjingwen6@huawei.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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