From: Jani Nikula <jani.nikula@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Dave Airlie <airlied@gmail.com>
Cc: Thierry Reding <treding@nvidia.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: panels: Add MAINTAINERS entry for LVS panel driver
Date: Wed, 05 Apr 2017 10:47:02 +0300 [thread overview]
Message-ID: <87efx71ekp.fsf@intel.com> (raw)
In-Reply-To: <1677800.oe9lZ3jeP6@avalon>
On Wed, 05 Apr 2017, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> Hi Dave,
>
> On Wednesday 05 Apr 2017 09:51:27 Laurent Pinchart wrote:
>> As the DRM LVDS panel driver uses a different approach to DT bindings
>> compared to what Thierry Reding advocates, add a specific MAINTAINERS
>> entry to avoid bothering Thierry with requests related to that driver.
>>
>> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>
> Could you take this patch manually as part of "[GIT PULL FOR v4.12] Renesas R-
> Car Gen3 DU HDMI support" or should I resend the pull request ?
Or send a separate fixes pull for drm-next/-rc1 later?
BR,
Jani.
>
>> ---
>> MAINTAINERS | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index fa8479e1799a..88eaaec064ca 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -4209,6 +4209,14 @@ F: drivers/gpu/drm/panel/
>> F: include/drm/drm_panel.h
>> F: Documentation/devicetree/bindings/display/panel/
>>
>> +DRM LVDS PANEL DRIVER
>> +M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>> +L: dri-devel@lists.freedesktop.org
>> +T: git git://people.freedesktop.org/~airlied/linux
>> +S: Maintained
>> +F: drivers/gpu/drm/panel/panel-lvds.c
>> +F: Documentation/devicetree/bindings/display/panel/panel-lvds.txt
>> +
>> INTEL DRM DRIVERS (excluding Poulsbo, Moorestown and derivative chipsets)
>> M: Daniel Vetter <daniel.vetter@intel.com>
>> M: Jani Nikula <jani.nikula@linux.intel.com>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-05 7:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 14:17 [GIT PULL FOR v4.12] Renesas R-Car Gen3 DU HDMI support Laurent Pinchart
2017-04-04 15:21 ` Thierry Reding
2017-04-04 15:38 ` Laurent Pinchart
2017-04-04 16:03 ` Daniel Vetter
2017-04-07 17:40 ` Thierry Reding
2017-04-05 6:51 ` [PATCH] drm: panels: Add MAINTAINERS entry for LVS panel driver Laurent Pinchart
2017-04-05 6:56 ` Laurent Pinchart
2017-04-05 7:47 ` Jani Nikula [this message]
2017-04-06 19:44 ` Dave Airlie
2017-04-07 17:33 ` Thierry Reding
2017-04-09 12:31 ` Emil Velikov
2017-04-10 7:17 ` Thierry Reding
2017-04-10 9:03 ` Laurent Pinchart
2017-04-10 19:27 ` Dave Airlie
2017-04-11 4:41 ` Laurent Pinchart
2017-04-11 18:56 ` Rob Herring
2017-04-12 15:44 ` Thierry Reding
2017-04-12 17:42 ` Daniel Vetter
2017-04-12 19:46 ` Alex Deucher
2017-04-10 9:58 ` Lucas Stach
2017-04-10 11:38 ` Emil Velikov
2017-04-11 5:00 ` Laurent Pinchart
2017-04-11 10:03 ` Thierry Reding
2017-04-11 17:10 ` Rob Herring
2017-04-12 15:26 ` Thierry Reding
2017-04-12 23:27 ` Rob Herring
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=87efx71ekp.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--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