From: Harry Wentland <harry.wentland@amd.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David (ChunMing) Zhou" <David1.Zhou@amd.com>,
"David Airlie" <airlied@linux.ie>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
amd-gfx@lists.freedesktop.org,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amd/display: fix incompatible structure layouts
Date: Fri, 2 Feb 2018 11:08:03 -0500 [thread overview]
Message-ID: <0e880a52-768e-c476-84a5-3e9638b62f1b@amd.com> (raw)
In-Reply-To: <CAK8P3a3WN6VdJuEt=0nvC-8FCiOAVo8R=aRso4=C-jwM4rdQPQ@mail.gmail.com>
On 2018-02-02 11:02 AM, Arnd Bergmann wrote:
> On Fri, Feb 2, 2018 at 4:39 PM, Harry Wentland <harry.wentland@amd.com> wrote:
>> On 2018-02-02 07:31 AM, Arnd Bergmann wrote:
>>> Building the amd display driver with link-time optimizations revealed a bug
>>
>> Curious how I'd go about building with link-time optimizations.
>
> I got the idea from last week's LWN article on the topic, see
> https://lwn.net/Articles/744507/. I needed the latest gcc version to
> avoid some compiler bugs, and a few dozen kernel patches on top
> to get a clean build in random configurations (posted them all today).
>
> Most normal configurations probably work out of the box, but I have
> not actually tried running any ;-)
>
Thanks. Learn something new every day. I like this bit from the article:
> So it is basically just like if it concatenated all source files into a single one and made everything static.
Probably not a bad idea to think that way when doing kernel development. :)
Harry
> Arnd
>
prev parent reply other threads:[~2018-02-02 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 12:31 Arnd Bergmann
2018-02-02 15:39 ` Harry Wentland
2018-02-02 16:02 ` Arnd Bergmann
2018-02-02 16:08 ` Harry Wentland [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=0e880a52-768e-c476-84a5-3e9638b62f1b@amd.com \
--to=harry.wentland@amd.com \
--cc=David1.Zhou@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arnd@arndb.de \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®