dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFC] MAINTAINERS: Add Sam as reviewer for drm/panel
Date: Wed, 17 Apr 2019 11:02:32 +0200	[thread overview]
Message-ID: <20190417090232.GA26568@ravnborg.org> (raw)
In-Reply-To: <20190416075910.12015-1-thierry.reding@gmail.com>

Hi Thierry.

On Tue, Apr 16, 2019 at 09:59:10AM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Sam has been helping out a lot with reviewing DRM panel patches. Add him
> as reviewer to help him do this important work.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c227d2818c98..3d199592fd2c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5340,6 +5340,7 @@ T:	git git://anongit.freedesktop.org/drm/drm-misc
>  
>  DRM PANEL DRIVERS
>  M:	Thierry Reding <thierry.reding@gmail.com>
> +R:	Sam Ravnborg <sam@ravnborg.org>
>  L:	dri-devel@lists.freedesktop.org
>  T:	git git://anongit.freedesktop.org/drm/drm-misc
>  S:	Maintained

I'm pretending that I know a little about the drm/panel/ subsystem,
so this makes good sense.
My response time will be decided on my day-job, but this is
like is is for all os us.

I will push the patch myself when I am back in the weekend.
(To try out the dim tooling etc).

	Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-04-17  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16  7:59 [RFC] MAINTAINERS: Add Sam as reviewer for drm/panel Thierry Reding
2019-04-16  8:02 ` Jagan Teki
2019-04-17  9:02 ` Sam Ravnborg [this message]
2019-04-22 19:24   ` Sam Ravnborg

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=20190417090232.GA26568@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=thierry.reding@gmail.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