[PATCH] MAINTAINERS: Add dri-devel for component.[hc]

Daniel Vetter daniel at ffwll.ch
Thu Aug 26 19:39:44 UTC 2021


On Thu, Aug 26, 2021 at 12:56:26PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Aug 26, 2021 at 11:13:43AM +0200, Daniel Vetter wrote:
> > dri-devel is the main user, and somehow there's been the assumption
> > that component stuff is unmaintained.
> > 
> > References: https://lore.kernel.org/dri-devel/CAAEAJfDWOzCJxZFNtxeT7Cvr2pWbYrfz-YnA81sVNs-rM=8n4Q@mail.gmail.com/
> > Cc: Ezequiel Garcia <ezequiel at vanguardiasur.com.ar>
> > Cc: Greg Kroah-Hartman <gregkh at linuxfoundation.org>
> > Cc: "Rafael J. Wysocki" <rafael at kernel.org>
> > Signed-off-by: Daniel Vetter <daniel.vetter at intel.com>
> > ---
> >  MAINTAINERS | 5 +++++
> >  1 file changed, 5 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index ac58d0032abd..7cdc19815ec4 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -5707,6 +5707,11 @@ F:	Documentation/admin-guide/blockdev/
> >  F:	drivers/block/drbd/
> >  F:	lib/lru_cache.c
> >  
> > +DRIVER COMPONENT FRAMEWORK
> > +L:	dri-devel at lists.freedesktop.org
> > +F:	drivers/base/component.c
> > +F:	include/linux/component.h
> 
> Acked-by: Greg Kroah-Hartman <gregkh at linuxfoundation.org>

Will you merge this through your tree? I think merging component patches
through driver core makes sense (or topic branch or whatever) still. This
is just so that there's a wider reviewer pool than just you & Rafael.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch


More information about the dri-devel mailing list