From: Dave Airlie <airlied@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm next for 5.9-rc1
Date: Thu, 6 Aug 2020 12:28:25 +1000 [thread overview]
Message-ID: <CAPM=9tx5bMLofaA75ZrBwdjAF-ZpQ3xU+pf5QGKJakLUQYNKNg@mail.gmail.com> (raw)
In-Reply-To: <CAPM=9ty8hOY0m2+RJdRiRADY5Li-hs3ZaDEK-DTf6rgFewar7g@mail.gmail.com>
On Thu, 6 Aug 2020 at 11:07, Dave Airlie <airlied@gmail.com> wrote:
>
> Hi Linus,
>
> This the main drm pull request for 5.9-rc1.
>
> New xilinx displayport driver, AMD support for two new GPUs (more
> header files), i915 initial support for RocketLake and some work on
> their DG1 (discrete chip).
>
> The core also grew some lockdep annotations to try and constrain what
> drivers do with dma-fences, and added some documentation on why the
> idea of indefinite fences doesn't work.
>
> The long list is below.
>
> I did a test merge into your tree and only had two minor conflicts, so
> I think you should be able to take care of it fine.
I should say I did a test merge yesterday, but you likely pulled more trees,
https://lore.kernel.org/dri-devel/20200806115140.6aa46042@canb.auug.org.au/T/#t
So there was an unfortunate miscommunication and one patch went two
ways, in future Jason and Ben will coordinate better.
Dave.
next prev parent reply other threads:[~2020-08-06 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 1:07 [git pull] drm next for 5.9-rc1 Dave Airlie
2020-08-06 2:28 ` Dave Airlie [this message]
2020-08-06 3:08 ` pr-tracker-bot
2020-08-10 12:23 ` Christoph Hellwig
2020-08-10 18:45 ` Dave Airlie
2020-08-10 22:55 ` Ben Skeggs
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='CAPM=9tx5bMLofaA75ZrBwdjAF-ZpQ3xU+pf5QGKJakLUQYNKNg@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@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).