From: Randy Dunlap <rdunlap@infradead.org>
To: Harry Wentland <hwentlan@amd.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Wentland, Harry" <Harry.Wentland@amd.com>,
"Li, Sun peng (Leo)" <Sunpeng.Li@amd.com>
Subject: Re: linux-next: Tree for Sep 4 (amd/display/)
Date: Thu, 5 Sep 2019 07:54:28 -0700 [thread overview]
Message-ID: <d29463cd-0497-41f2-a502-110b02c7abc8@infradead.org> (raw)
In-Reply-To: <752f74d6-f6ff-6013-25ad-a8fdce934d17@amd.com>
On 9/5/19 6:17 AM, Harry Wentland wrote:
>
>
> On 2019-09-04 4:58 p.m., Randy Dunlap wrote:
>> On 9/4/19 6:34 AM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> News: this will be the last linux-next I will release until Sept 30.
>>>
>>> Changes since 20190903:
>>>
>>
>> on x86_64:
>>
>> In file included from ../drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn20/display_rq_dlg_calc_20v2.c:77:0:
>> ../drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn20/../dml_inline_defs.h: In function ‘dml_min’:
>> ../drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn20/../dml_inline_defs.h:34:1: error: SSE register return with SSE disabled
>>
>
> Is that fixed by Stephen's fixup here?
>
> https://lists.freedesktop.org/archives/dri-devel/2019-September/234292.html
That patch is already in linux-next, so No, it's not.
I am using:
> gcc --version
gcc (SUSE Linux) 7.4.1 20190424 [gcc-7-branch revision 270538]
--
~Randy
next prev parent reply other threads:[~2019-09-05 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 13:34 linux-next: Tree for Sep 4 Stephen Rothwell
2019-09-04 20:58 ` linux-next: Tree for Sep 4 (amd/display/) Randy Dunlap
2019-09-05 13:17 ` Harry Wentland
2019-09-05 14:54 ` Randy Dunlap [this message]
2019-09-17 3:42 ` Kees Cook
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=d29463cd-0497-41f2-a502-110b02c7abc8@infradead.org \
--to=rdunlap@infradead.org \
--cc=Harry.Wentland@amd.com \
--cc=Sunpeng.Li@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hwentlan@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®