From: "Jingoo Han" <jingoohan1@gmail.com>
To: "'Daniel Thompson'" <daniel.thompson@linaro.org>,
"'Daniel Vetter'" <daniel.vetter@ffwll.ch>,
"'DRI Development'" <dri-devel@lists.freedesktop.org>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>,
"'Lee Jones'" <lee.jones@linaro.org>,
"'Daniel Vetter'" <daniel.vetter@intel.com>
Subject: Re: [PATCH 6/6] MAINTAINERS: add dri-devel for backlight subsystem patches
Date: Wed, 17 Jan 2018 12:06:26 -0500 [thread overview]
Message-ID: <001a01d38fb5$8386d2e0$8a9478a0$@gmail.com> (raw)
In-Reply-To: <83974622-65bc-29ea-ac3d-954aa15f3779@linaro.org>
On Wednesday, January 17, 2018 11:53 AM, Daniel Thompson wrote:
> On 17/01/18 14:01, Daniel Vetter wrote:
> > For the same reasons we've added dri-devel for all fbdev patches: Most
> > of the actively developed drivers using this infrastructure are in
> > drivers/gpu/. It just makes sense to cross-post patches and keep
> > aligned. And total activity in the backlight subsystem is miniscule
> > compared to drm overall.
> >
> > Cc: Lee Jones <lee.jones@linaro.org>
> > Cc: Daniel Thompson <daniel.thompson@linaro.org>
> > Cc: Jingoo Han <jingoohan1@gmail.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>
> Acked-by: Daniel Thompson <daniel.thompson@linaro.org>
Acked-by: Jingoo Han <jingoohan1@gmail.com>
Best regards,
Jingoo Han
>
>
> > ---
> > MAINTAINERS | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 7691e1025708..6534517f53b6 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -2546,6 +2546,7 @@ BACKLIGHT CLASS/SUBSYSTEM
> > M: Lee Jones <lee.jones@linaro.org>
> > M: Daniel Thompson <daniel.thompson@linaro.org>
> > M: Jingoo Han <jingoohan1@gmail.com>
> > +L: dri-devel@lists.freedesktop.org
> > T: git git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
> > S: Maintained
> > F: drivers/video/backlight/
> >
next prev parent reply other threads:[~2018-01-17 17:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 14:01 [PATCH 1/6] backlight: Nuke unused backlight.props.state states Daniel Vetter
2018-01-17 14:01 ` [PATCH 2/6] backlight/generic-bl: remove DRIVER1 state Daniel Vetter
2018-01-17 14:36 ` Emil Velikov
2018-01-17 16:37 ` Daniel Thompson
2018-01-18 13:08 ` Emil Velikov
2018-01-17 16:44 ` Daniel Thompson
2018-01-17 17:13 ` Daniel Vetter
2018-01-18 9:20 ` Daniel Thompson
2018-01-17 14:01 ` [PATCH 3/6] backlight/pandora: Stop using BL_CORE_DRIVER1 Daniel Vetter
2018-01-17 16:47 ` Daniel Thompson
2018-01-17 21:38 ` Daniel Vetter
2018-01-18 9:42 ` Daniel Thompson
2018-01-17 14:01 ` [PATCH 4/6] staging/fbtft: " Daniel Vetter
2018-01-17 16:50 ` Daniel Thompson
2018-01-17 14:01 ` [PATCH 5/6] backlight: Also nuke BL_CORE_DRIVER1 Daniel Vetter
2018-01-17 16:51 ` Daniel Thompson
2018-01-17 14:01 ` [PATCH 6/6] MAINTAINERS: add dri-devel for backlight subsystem patches Daniel Vetter
2018-01-17 16:52 ` Daniel Thompson
2018-01-17 17:06 ` Jingoo Han [this message]
2018-01-17 14:56 ` [PATCH 1/6] backlight: Nuke unused backlight.props.state states Daniel Thompson
2018-01-18 8:32 ` Lee Jones
2018-04-25 17:42 Daniel Vetter
2018-04-25 17:42 ` [PATCH 6/6] MAINTAINERS: add dri-devel for backlight subsystem patches Daniel Vetter
2018-04-25 19:43 ` Jingoo Han
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='001a01d38fb5$8386d2e0$8a9478a0$@gmail.com' \
--to=jingoohan1@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome