From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: A change of approach
Date: Mon, 06 Aug 2007 22:59:06 +0000 [thread overview]
Message-ID: <20070806225906.GA9732@parisc-linux.org> (raw)
In-Reply-To: <20070731220505.GT21219@parisc-linux.org>
On Mon, Aug 06, 2007 at 07:20:00PM +0200, Andi Drebes wrote:
> Hi Darren,
> > I was just wondering about finding an unmaintained driver. Should we
> > just look for
> > stuff marked as Orphan in the MAINTAINERS file or is there
> > another/better list/way
> > to find an un-maintained driver that we shuld be made aware of?
Better is to find drivers with no entry in the MAINTAINERS file at all
... though that's hard to do reliably. If you announce to K-J that you
intend to take on a driver, someone with a bit more experience such as
Randy or myself can probably let you know if that driver has a maintainer.
> I don't think that the driver definitely has to be unmaintained in order to be
> chosen by a kernel janitor. If you pick a driver that is currently
> maintained, you could do the janitorial work and send a series of patches to
> the maintainer and to the list. I think a maintainer would appreciate this
> because somebody does the "dirty work".
That's going to vary by maintainer -- people are funny that way.
Definitely have a thick skin if you're going to do this. I know how
frustrating it is if you've put in a lot of work cleaning up a driver,
only to have the maintainer reject it because "this driver has to work
on $otheros too, and they don't have a $foo".
I'm glad you two have taken my frustrated comment in such a positive
way. Thanks.
--
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-08-06 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 22:05 A change of approach Matthew Wilcox
2007-08-04 6:30 ` Darren Jenkins
2007-08-06 17:20 ` Andi Drebes
2007-08-06 22:59 ` Matthew Wilcox [this message]
2007-08-07 7:05 ` Thomas Petazzoni
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=20070806225906.GA9732@parisc-linux.org \
--to=matthew@wil.cx \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.