From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@gmail.com>
Cc: Linus <torvalds@linux-foundation.org>,
Dave Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: Large new drm driver
Date: Tue, 2 May 2017 12:57:43 +1000 [thread overview]
Message-ID: <20170502125743.1d79c007@canb.auug.org.au> (raw)
In-Reply-To: <CAPM=9tw+v7+Ps_siHEdg9QHLEYLR81VGRMPL+7+p1ntFCnCOLQ@mail.gmail.com>
Hi Dave,
On Tue, 2 May 2017 12:36:35 +1000 Dave Airlie <airlied@gmail.com> wrote:
>
> We've had register header files like this on a number of occasions
> before, not sure why it warrants a mention now.
Linus expressed suprise once before when we had a large number of new
lines appear in another subsystem ...
> It's just the public header files for the new Vega AMD GPUs,
> as opposed to a whole new driver.
>
> AMD release the validated headers so open source developers
> don't have to go hunting for registers.
It's all fine, just noting.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-05-02 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 1:31 Large new drm driver Stephen Rothwell
2017-05-02 2:36 ` Dave Airlie
2017-05-02 2:57 ` Stephen Rothwell [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=20170502125743.1d79c007@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).