From: Jason Gunthorpe <jgg@mellanox.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jerome Glisse <jglisse@redhat.com>,
Thomas Hellstrom <thellstrom@vmware.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: DRM pull for v5.3-rc1
Date: Mon, 15 Jul 2019 17:57:30 +0000 [thread overview]
Message-ID: <20190715175726.GC5043@mellanox.com> (raw)
In-Reply-To: <CAKMK7uGbNuA_pN=r9XKGz2MTVVJWm6q8tKBT3WJPa93nKEe4iA@mail.gmail.com>
On Mon, Jul 15, 2019 at 07:53:06PM +0200, Daniel Vetter wrote:
> > So, I'll put it on a topic and send you two a note next week to decide
> > if you want to merge it or not. I'm really unclear how nouveau's and
> > AMD's patchflow works..
>
> DRM is 2-level for pretty much everything. First it lands in a driver
> tree (or a collectiv of drivers, like in drm-misc). Then those send
> pull requests to drm.git for integration. Busy trees do that every 1-2
> weeks (e.g. amdgpu), slower trees once per merge window (e.g. nouveau)
> for drm-next, similar for drm-fixes.
The DRM part seems logical - it is how the AMD GPU and nouveau git
trees trees work that I don't know. I heard that neither could take in
a stable topic branch?
Jason
next prev parent reply other threads:[~2019-07-15 17:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPM=9tzJQ+26n_Df1eBPG1A=tXf4xNuVEjbG3aZj-aqYQ9nnAg@mail.gmail.com>
2019-07-15 7:08 ` drm pull for v5.3-rc1 Dave Airlie
2019-07-15 12:16 ` Daniel Vetter
2019-07-15 17:37 ` Linus Torvalds
2019-07-15 18:00 ` Linus Torvalds
2019-07-15 18:29 ` Dave Airlie
2019-07-15 18:37 ` Linus Torvalds
2019-07-15 19:35 ` Thomas Hellström (VMware)
2019-07-15 20:07 ` Linus Torvalds
2019-07-15 22:17 ` Linus Torvalds
2019-08-06 7:38 ` Christoph Hellwig
2019-08-06 7:40 ` Christoph Hellwig
2019-08-06 18:50 ` Linus Torvalds
2019-08-06 19:09 ` Matthew Wilcox
2019-08-07 6:40 ` Christoph Hellwig
2019-08-07 14:15 ` Matthew Wilcox
2019-08-07 14:30 ` Steven Price
2019-08-07 14:56 ` Matthew Wilcox
2019-08-07 15:32 ` Steven Price
2019-08-07 15:55 ` Matthew Wilcox
2019-08-07 19:16 ` Linus Torvalds
2019-08-07 6:38 ` Christoph Hellwig
2019-07-15 18:27 ` Dave Airlie
[not found] ` <CAPM=9tx+CEkzmLZ-93GZmde9xzJ_rw3PJZxFu_pjZJc7KM5f-w@mail.gmail.com>
2019-07-15 12:29 ` DRM " Jason Gunthorpe
2019-07-15 13:21 ` Stephen Rothwell
2019-07-15 14:19 ` Daniel Vetter
2019-07-15 15:04 ` Jason Gunthorpe
2019-07-15 17:53 ` Daniel Vetter
2019-07-15 17:57 ` Jason Gunthorpe [this message]
2019-07-15 18:06 ` Daniel Vetter
2019-07-15 18:16 ` Linus Torvalds
2019-07-15 19:00 ` Linus Torvalds
2019-07-15 19:17 ` Jason Gunthorpe
2019-07-15 19:31 ` Linus Torvalds
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=20190715175726.GC5043@mellanox.com \
--to=jgg@mellanox.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=thellstrom@vmware.com \
--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).