Re: [PATCH] MAINTAINERS: mark framebuffer as Orphan

[Randy Dunlap]

On Thu, 15 Feb 2007 22:26:10 +0000 (GMT) James Simmons wrote:

> 
> I wouldn't say it orphan. I just can't spend 8 hours a day on it. 
> Alot of patches have been flowing into the layer.

So would you like to leave it as Maintained or change it to
"Odd Fixes"?  (Maintained => a maintainer)  From the MAINTAINTERS file:

	Supported:	Someone is actually paid to look after this.
	Maintained:	Someone actually looks after it.
	Odd Fixes:	It has a maintainer but they don't have time to do
			much other than throw the odd patch in. See below..
	Orphan:		No current maintainer [but maybe you could take the
			role as you write your new code].
	Obsolete:	Old code. Something tagged obsolete generally means
			it has been replaced by a better system and you
			should be using that.


> On Thu, 15 Feb 2007, Randy Dunlap wrote:
> 
> > From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
> > 
> > Are we ready to do this?
> > I'd love for Tony to return, but he's been missing for awhile now.
> > 
> > So this give us the following major areas that are marked as Orphan:
> > 
> > Firmware loader
> > Framebuffer
> > Serial (8250/16x50)
> > 
> > and PCMCIA has a Team.  It doesn't seem to be hurting.  :)
> > 
> > Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
> > ---
> >  MAINTAINERS |    4 +---
> >  1 file changed, 1 insertion(+), 3 deletions(-)
> > 
> > --- linux-2.6.20-git9.orig/MAINTAINERS
> > +++ linux-2.6.20-git9/MAINTAINERS
> > @@ -1321,11 +1321,9 @@ W:	http://www.farsite.co.uk/
> >  S:	Supported
> >  
> >  FRAMEBUFFER LAYER
> > -P:	Antonino Daplas
> > -M:	adaplas@xxxxxxx
> >  L:	linux-fbdev-devel@xxxxxxxxxxxxxxxxxxxxx (subscribers-only)
> >  W:	http://linux-fbdev.sourceforge.net/
> > -S:	Maintained
> > +S:	Orphan
> >  
> >  FREESCALE SOC FS_ENET DRIVER
> >  P:	Pantelis Antoniou

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/