linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-fbdev@vger.kernel.org,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: remove current maintainer
Date: Tue, 20 Dec 2016 01:17:36 +0000	[thread overview]
Message-ID: <5102616.aqlTlCbrFA@avalon> (raw)
In-Reply-To: <20161208100447.cyidy3l2vtn6ozfs@phenom.ffwll.local>

Hi Daniel,

On Thursday 08 Dec 2016 11:04:47 Daniel Vetter wrote:
> On Thu, Dec 08, 2016 at 10:34:12AM +0200, Tomi Valkeinen wrote:
> > Remove Tomi Valkeinen from fbdev maintainer and mark fbdev as orphan.
> > 
> > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> > ---
> > 
> > I just don't have time to even pretend I maintain fbdev, so mark it as
> > Orphan.
> > 
> > Anyone want to pick fbdev maintainership?
> 
> I think for fbdev stuff that we need for the fbdev emulation in drm we
> could merge it through drm-misc.

Or we could instead invest time on getting rid of that last dependency on 
fbdev ? :-)

> And I'd very much welcome if you can
> still review those patches (e.g. the nommu enabling that's floating right
> now). If you want can also give you commit rights to drm-misc for that
> area. Or drm-misc maintainers can apply those patches.
> 
> Anything else would be still out of scope ofc.
> 
> What we might want to do is add dri-devel to the mailing lists, to make
> sure patch submissions get redicted to the right subsystem. Mail volume
> seems pretty low compared to dri-devel, I think we can absorb that.
> -Daniel
> 
> >  MAINTAINERS | 3 +--
> >  1 file changed, 1 insertion(+), 2 deletions(-)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 851b89b9edcb..fc2790eb4e84 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -4968,10 +4968,9 @@ F:	drivers/net/wan/dlci.c
> > 
> >  F:	drivers/net/wan/sdla.c
> >  
> >  FRAMEBUFFER LAYER
> > 
> > -M:	Tomi Valkeinen <tomi.valkeinen@ti.com>
> > 
> >  L:	linux-fbdev@vger.kernel.org
> >  Q:	http://patchwork.kernel.org/project/linux-fbdev/list/
> > 
> > -S:	Maintained
> > +S:	Orphan
> > 
> >  F:	Documentation/fb/
> >  F:	drivers/video/
> >  F:	include/video/

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2016-12-20  1:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08  8:34 [PATCH] fbdev: remove current maintainer Tomi Valkeinen
2016-12-08 10:04 ` Daniel Vetter
2016-12-20  1:17   ` Laurent Pinchart [this message]
2016-12-15 20:12 ` Andrew Morton
2016-12-19 13:34   ` Bartlomiej Zolnierkiewicz
2016-12-19 18:13     ` Andrew Morton
2016-12-20 13:16     ` Tomi Valkeinen

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=5102616.aqlTlCbrFA@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).