From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
"# 3.4.x" <stable@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: Please apply commit 0f0727d971f6 ("drm/amd/display: readd -msse2 to prevent Clang from emitting libcalls to undefined SW FP routines") to 4.19.y
Date: Sun, 22 Sep 2019 17:09:14 -0400 [thread overview]
Message-ID: <20190922210914.GC8171@sasha-vm> (raw)
In-Reply-To: <20190922081638.GC2524798@kroah.com>
On Sun, Sep 22, 2019 at 10:16:38AM +0200, Greg KH wrote:
>On Tue, Aug 20, 2019 at 02:41:15PM -0700, Nick Desaulniers wrote:
>> On Tue, Aug 20, 2019 at 2:35 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>> >
>> > On Tue, Aug 20, 2019 at 05:25:39PM -0400, Sasha Levin wrote:
>> > > On Tue, Aug 20, 2019 at 02:07:16PM -0700, Greg KH wrote:
>> > > > On Tue, Aug 20, 2019 at 02:00:21PM -0700, Nick Desaulniers wrote:
>> > > > > Please apply commit 0f0727d971f6 ("drm/amd/display: readd -msse2 to
>> > > > > prevent Clang from emitting libcalls to undefined SW FP routines") to
>> > > > > 4.19.y.
>> > > > >
>> > > > > It will help with AMD based chromebooks for ChromeOS.
>> > > >
>> > > > That commit id is not in Linus's tree, are you sure you got it correct?
>> > >
>> > > That's a linux-next commit.
>> >
>> > Great, we can wait for it to show up in Linus's tree first :)
>>
>> *checks tree*
>> Oh yeah, oops. Sorry for the noise.
>
>It's in Linus's tree now, but it does not apply to 5.2.y or 4.19.y, so
>can you provide a working backport for those kernels?
Looks like it was mostly due to missing 7ed4e6352c16f ("drm/amd/display:
Add DCN2 HW Sequencer and Resource") on older kernels. I've fixed it up
and queued it up.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-09-22 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 21:00 Please apply commit 0f0727d971f6 ("drm/amd/display: readd -msse2 to prevent Clang from emitting libcalls to undefined SW FP routines") to 4.19.y Nick Desaulniers
2019-08-20 21:07 ` Greg KH
2019-08-20 21:25 ` Sasha Levin
2019-08-20 21:35 ` Greg KH
2019-08-20 21:41 ` Nick Desaulniers
2019-09-22 8:16 ` Greg KH
2019-09-22 21:09 ` Sasha Levin [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=20190922210914.GC8171@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=ndesaulniers@google.com \
--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