[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1432139296.2870.305.camel@perches.com>
Date: Wed, 20 May 2015 09:28:16 -0700
From: Joe Perches <joe@...ches.com>
To: Richard Weinberger <richard.weinberger@...il.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Tim Waugh <tim@...erelk.net>, Jean Delvare <jdelvare@...e.de>,
Wolfram Sang <wsa@...-dreams.de>,
Willy Tarreau <willy@...a-x.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Cox <gnomes@...rguk.ukuu.org.uk>,
LKML <linux-kernel@...r.kernel.org>, linux-i2c@...r.kernel.org,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>
Subject: Re: [PATCH 6/6] MAINTAINERS: maintain parport
On Wed, 2015-05-20 at 17:46 +0200, Richard Weinberger wrote:
> On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee
> <sudipm.mukherjee@...il.com> wrote:
> > Lets give the parport subsystem a proper name and start
> > maintaining the files.
>
> Excuse me, but usually someone takes over the maintainer role after
> proving that he
> cares for a sub system for a certain period of time.
> Or did I miss something?
MAINTAINERS:85: Orphan: No current maintainer [but maybe you could take the
MAINTAINERS-86- role as you write your new code].
Parport is an orphan, hasn't had a maintainer since at
least 2.6.12, and has almost no activity minus drive-by
cleanups and new device ID support every once in awhile.
Sudip is writing new code.
If Sudip wants to be a maintainer of parport, assuming
he has the time and resources to give it a go, I think
he should be welcomed to it.
Thanks Sudip. Best of luck...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists