All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: christian.koenig@amd.com
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] MAINTAINERS: add separate entry for DRM TTM
Date: Thu, 14 Dec 2017 21:05:50 +0100	[thread overview]
Message-ID: <20171214200550.GL26573@phenom.ffwll.local> (raw)
In-Reply-To: <051a4726-4800-95ec-2bf9-0666b00ee8b1@gmail.com>

On Thu, Dec 14, 2017 at 04:15:27PM +0100, Christian König wrote:
> Am 14.12.2017 um 15:41 schrieb Daniel Vetter:
> > On Thu, Dec 14, 2017 at 08:45:10AM -0500, Alex Deucher wrote:
> > > On Thu, Dec 14, 2017 at 8:37 AM, Christian König
> > > <ckoenig.leichtzumerken@gmail.com> wrote:
> > > > AMD is the major user of TTM, so it also makes sense that we maintain
> > > > it.
> > > > 
> > > > Signed-off-by: Christian König <christian.koenig@amd.com>
> > > Acked-by: Alex Deucher <alexander.deucher@amd.com>
> > > 
> > > > ---
> > > >   MAINTAINERS | 8 ++++++++
> > > >   1 file changed, 8 insertions(+)
> > > > 
> > > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > > index 069ba63190b2..72e8f8f750ec 100644
> > > > --- a/MAINTAINERS
> > > > +++ b/MAINTAINERS
> > > > @@ -4805,6 +4805,14 @@ S:       Maintained
> > > >   F:     drivers/gpu/drm/tinydrm/
> > > >   F:     include/drm/tinydrm/
> > > > 
> > > > +DRM TTM SUBSYSTEM
> > > > +M:     Christian Koenig <christian.koenig@amd.com>
> > > > +M:     Roger He <Hongbo.He@amd.com>
> > > > +S:     Maintained
> > > > +L:     dri-devel@lists.freedesktop.org
> > > > +F:     include/drm/ttm/
> > > > +F:     drivers/gpu/drm/ttm/
> > A git tree would be good here I think. Defacto that's right now the amd
> > tree.
> 
> Yeah, I was wondering what to do with that as well.
> 
> I see three possible options of hand:
> A) Stick with the amd trees maintained by Alex.
> B) Come up with separate ones.
> C) Use drm-misc.
> 
> For now I think I will stick with A if there are no objections.

For C, would be happy to add Roger He as committer if there's a need.
Assuming you make sure he writes good commit message ofc :-)
-Daniel

> 
> Christian.
> 
> > -Daniel
> > 
> > > > +
> > > >   DSBR100 USB FM RADIO DRIVER
> > > >   M:     Alexey Klimov <klimov.linux@gmail.com>
> > > >   L:     linux-media@vger.kernel.org
> > > > --
> > > > 2.11.0
> > > > 
> > > > _______________________________________________
> > > > dri-devel mailing list
> > > > dri-devel@lists.freedesktop.org
> > > > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> > > _______________________________________________
> > > dri-devel mailing list
> > > dri-devel@lists.freedesktop.org
> > > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> 

-- 
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:[~2017-12-14 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 13:37 [PATCH] MAINTAINERS: add separate entry for DRM TTM Christian König
2017-12-14 13:45 ` Alex Deucher
2017-12-14 14:41   ` Daniel Vetter
2017-12-14 15:15     ` Christian König
2017-12-14 20:05       ` Daniel Vetter [this message]
2017-12-14 17:48 ` Emil Velikov
2017-12-14 17:55   ` Thomas Hellstrom

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=20171214200550.GL26573@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.