All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: Thierry Reding <treding@nvidia.com>,
	open list <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/5] MAINTAINERS: Add entry for MIPI DSI bus
Date: Mon, 27 Oct 2014 19:53:08 +0100	[thread overview]
Message-ID: <20141027185308.GS26941@phenom.ffwll.local> (raw)
In-Reply-To: <544E62B5.8060603@samsung.com>

On Mon, Oct 27, 2014 at 04:20:21PM +0100, Andrzej Hajda wrote:
> On 10/27/2014 03:17 PM, Daniel Vetter wrote:
> > On Mon, Oct 27, 2014 at 10:48:26AM +0100, Andrzej Hajda wrote:
> >> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
> >> ---
> >>  MAINTAINERS | 7 +++++++
> >>  1 file changed, 7 insertions(+)
> >>
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index dd31933..476679c 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -3071,6 +3071,13 @@ F:	drivers/gpu/vga/
> >>  F:	include/drm/
> >>  F:	include/uapi/drm/
> >>  
> >> +DRM MIPI DSI BUS
> >> +M:	Andrzej Hajda <a.hajda@samsung.com>
> >> +L:	dri-devel@lists.freedesktop.org
> >> +S:	Supported
> >> +F:	drivers/gpu/drm/drm_mipi_dsi.c
> >> +F:	include/drm/drm_mipi_dsi.h
> > 
> > I really prefer when common infrastructure like this doesn't get
> > maintainer by a vendor. And I care with my intel hat on since we also ahve
> > a dsi driver that sooner or later needs to be converted to to this stuff.
> > 
> > Why doesn't the usual model of merging stuff through Dave's tree, or if
> > that doesn't work well due to patch depencies, through vendor trees with
> > Dave's ack?
> 
> The main intention of this patch is to be on CC in case of patches
> touching MIPI DSI bus.
> I do not want to create separate tree for such small subsystem.
> 
> So if such things are not allowed please drop the patch and sorry for
> the noise.

For that stuff you can just create a mail filter that shovels everything
touching anything dsi related on dri-devel (people arleady should send all
stuff there anyway) into a special folder/mark it as important. If you
rely on people to always use get_maintainers.pl that won't work properly
anyway.

So if all you want is to notice all dsi related patches then adding a
maintainer entry isn't a good solution anyway. So best to drop this one.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: Dave Airlie <airlied@gmail.com>,
	dri-devel@lists.freedesktop.org,
	Thierry Reding <treding@nvidia.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] MAINTAINERS: Add entry for MIPI DSI bus
Date: Mon, 27 Oct 2014 19:53:08 +0100	[thread overview]
Message-ID: <20141027185308.GS26941@phenom.ffwll.local> (raw)
In-Reply-To: <544E62B5.8060603@samsung.com>

On Mon, Oct 27, 2014 at 04:20:21PM +0100, Andrzej Hajda wrote:
> On 10/27/2014 03:17 PM, Daniel Vetter wrote:
> > On Mon, Oct 27, 2014 at 10:48:26AM +0100, Andrzej Hajda wrote:
> >> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
> >> ---
> >>  MAINTAINERS | 7 +++++++
> >>  1 file changed, 7 insertions(+)
> >>
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index dd31933..476679c 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -3071,6 +3071,13 @@ F:	drivers/gpu/vga/
> >>  F:	include/drm/
> >>  F:	include/uapi/drm/
> >>  
> >> +DRM MIPI DSI BUS
> >> +M:	Andrzej Hajda <a.hajda@samsung.com>
> >> +L:	dri-devel@lists.freedesktop.org
> >> +S:	Supported
> >> +F:	drivers/gpu/drm/drm_mipi_dsi.c
> >> +F:	include/drm/drm_mipi_dsi.h
> > 
> > I really prefer when common infrastructure like this doesn't get
> > maintainer by a vendor. And I care with my intel hat on since we also ahve
> > a dsi driver that sooner or later needs to be converted to to this stuff.
> > 
> > Why doesn't the usual model of merging stuff through Dave's tree, or if
> > that doesn't work well due to patch depencies, through vendor trees with
> > Dave's ack?
> 
> The main intention of this patch is to be on CC in case of patches
> touching MIPI DSI bus.
> I do not want to create separate tree for such small subsystem.
> 
> So if such things are not allowed please drop the patch and sorry for
> the noise.

For that stuff you can just create a mail filter that shovels everything
touching anything dsi related on dri-devel (people arleady should send all
stuff there anyway) into a special folder/mark it as important. If you
rely on people to always use get_maintainers.pl that won't work properly
anyway.

So if all you want is to notice all dsi related patches then adding a
maintainer entry isn't a good solution anyway. So best to drop this one.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-10-27 18:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  9:48 [PATCH 0/5] MAINTAINERS: add entries for few DRM drivers Andrzej Hajda
2014-10-27  9:48 ` Andrzej Hajda
2014-10-27  9:48 ` [PATCH 1/5] MAINTAINERS: Add entry for MIPI DSI bus Andrzej Hajda
2014-10-27  9:48   ` Andrzej Hajda
2014-10-27 14:17   ` Daniel Vetter
2014-10-27 14:17     ` Daniel Vetter
2014-10-27 15:20     ` Andrzej Hajda
2014-10-27 15:20       ` Andrzej Hajda
2014-10-27 18:53       ` Daniel Vetter [this message]
2014-10-27 18:53         ` Daniel Vetter
2014-10-29 12:39     ` Thierry Reding
2014-10-29 12:39       ` Thierry Reding
2014-10-27  9:48 ` [PATCH 2/5] MAINTAINERS: Add entry for LD9040 drm panel driver Andrzej Hajda
2014-10-27  9:48   ` Andrzej Hajda
2014-10-27  9:48 ` [PATCH 3/5] MAINTAINERS: Add entry for S6E8AA0 " Andrzej Hajda
2014-10-27  9:48   ` Andrzej Hajda
2014-10-27  9:48 ` [PATCH 4/5] MAINTAINERS: Add entry for Exynos MIPI DSI DRM driver Andrzej Hajda
2014-10-27  9:48   ` Andrzej Hajda
2014-10-27  9:48 ` [PATCH 5/5] MAINTAINERS: Add entry for Exynos MIPI DPI " Andrzej Hajda
2014-10-27  9:48   ` Andrzej Hajda

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=20141027185308.GS26941@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=a.hajda@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=treding@nvidia.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 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.