From: Daniel Vetter <daniel@ffwll.ch>
To: Andrzej Hajda <a.hajda@samsung.com>, Dave Airlie <airlied@gmail.com>
Cc: 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 15:17:17 +0100 [thread overview]
Message-ID: <20141027141717.GN26941@phenom.ffwll.local> (raw)
In-Reply-To: <1414403310-6316-2-git-send-email-a.hajda@samsung.com>
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?
Thanks, Daniel
> +
> RADEON DRM DRIVERS
> M: Alex Deucher <alexander.deucher@amd.com>
> M: Christian König <christian.koenig@amd.com>
> --
> 1.9.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-10-27 14:17 UTC|newest]
Thread overview: 10+ 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 ` [PATCH 1/5] MAINTAINERS: Add entry for MIPI DSI bus Andrzej Hajda
2014-10-27 14:17 ` Daniel Vetter [this message]
2014-10-27 15:20 ` Andrzej Hajda
2014-10-27 18:53 ` Daniel Vetter
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 ` [PATCH 3/5] MAINTAINERS: Add entry for S6E8AA0 " 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 ` [PATCH 5/5] MAINTAINERS: Add entry for Exynos MIPI DPI " 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=20141027141717.GN26941@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=a.hajda@samsung.com \
--cc=airlied@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®