dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Dirk Hohndel <dirk@hohndel.org>
Cc: "Thomas Hellstrom" <thellstrom@vmware.com>,
	"Thomas Gleixner" <tglx@tglx.de>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org,
	"Dave Airlie" <airlied@redhat.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: drm SPDX updates
Date: Mon, 14 May 2018 18:31:31 +0200	[thread overview]
Message-ID: <20180514163131.GF28661@phenom.ffwll.local> (raw)
In-Reply-To: <20180514151029.GM1309@rrmbpvm.gr8dns.org>

On Mon, May 14, 2018 at 08:10:29AM -0700, Dirk Hohndel wrote:
> On Mon, May 14, 2018 at 05:01:43PM +0200, Thomas Hellstrom wrote:
> > > I haven't seen any comments in the week since I wrote this. I'm not
> > > familiar with the process for the drm changes - so what are the usual next
> > > steps? Do I need to submit all or part of this somewhere else? Or does
> > > Dave simply take the series (since it has no executable code changes at
> > > all)?
> > 
> > There are a number of teams sending pull requests to Dave. One option would
> > be to have it all go through the drm-misc tree. (CC'ing Daniel Vetter about
> > that). Another option would perhaps be to send a pull request directly to
> > Dave (Dave?) And finally, one option would be to rely on the maintainers of
> > each submodule to take the patches that touch that module. If you go for
> > this last option, I can surely take the patches that touch vmwgfx, and
> > Christian the TTM patches.
> 
> Again, since this involves no code changes, I think I'd prefer the path
> directly via Dave, simply as it makes it more likely that none of them get
> lost... assuming you are willing to do that, Dave, where would you like that PR?

Cc: dri-devel and send it to Dave and you should be good. But I thought
Alex pulled this all in now? In the end probably doesn't matter really if
it gets merged twice :-)

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-05-14 16:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-06 23:16 drm SPDX updates Dirk Hohndel (VMware)
2018-05-06 23:16 ` [PATCH v2 1/8] drm: add SPDX idenitifier and clarify license Dirk Hohndel (VMware)
2018-05-06 23:16   ` [PATCH v2 2/8] drm/amd: add SPDX identifier " Dirk Hohndel (VMware)
2018-05-06 23:16     ` [PATCH v2 3/8] drm: " Dirk Hohndel (VMware)
2018-05-06 23:16       ` [PATCH v2 4/8] drm/noveau: " Dirk Hohndel (VMware)
2018-05-06 23:16         ` [PATCH v2 5/8] drm/radeon: " Dirk Hohndel (VMware)
2018-05-06 23:16           ` [PATCH v2 6/8] drm/ttm: add SPDX idenitifier " Dirk Hohndel (VMware)
2018-05-06 23:16             ` [PATCH v2 7/8] drm/vmwgfx: " Dirk Hohndel (VMware)
2018-05-06 23:16               ` [PATCH v2 8/8] " Dirk Hohndel (VMware)
2018-05-07 14:50               ` [PATCH v2 7/8] " Thomas Hellstrom
2018-05-07 17:23                 ` Dirk Hohndel
2018-05-08  9:57               ` Emil Velikov
2018-05-09  5:31                 ` Dirk Hohndel
2018-05-14  5:59 ` drm SPDX updates Thomas Gleixner
2018-05-14 14:54   ` Dirk Hohndel
2018-05-14 15:01     ` Thomas Hellstrom
2018-05-14 15:10       ` Dirk Hohndel
2018-05-14 16:31         ` Daniel Vetter [this message]
2018-05-15 19:53           ` Alex Deucher
2018-06-29 19:32             ` Alex Deucher
2018-06-29 19:36               ` Dirk Hohndel
2018-06-29 19:39                 ` Alex Deucher
2018-06-29 19:46                   ` Dirk Hohndel
2018-06-29 20:32                     ` Alex Deucher
  -- strict thread matches above, loose matches on Subject: below --
2018-05-03 22:15 Dirk Hohndel (VMware)

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=20180514163131.GF28661@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@redhat.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dirk@hohndel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tglx@tglx.de \
    --cc=thellstrom@vmware.com \
    /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