From: Adrian Bunk <bunk@stusta.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: mike@pikeaero.com, linux-kernel@vger.kernel.org
Subject: Re: maintainer: parport drivers
Date: Tue, 17 Jul 2007 19:12:36 +0200 [thread overview]
Message-ID: <20070717171236.GG3801@stusta.de> (raw)
In-Reply-To: <20070717095815.ae811965.randy.dunlap@oracle.com>
On Tue, Jul 17, 2007 at 09:58:15AM -0700, Randy Dunlap wrote:
> On Tue, 17 Jul 2007 12:09:16 -0400 Mike Sharkey wrote:
>
> > Hello,
> >
> > I understand there are currently no active maintainers of parport and
> > friends - unless that has changed recently.
> >
> > We are heavy users of parport devices, and so I am offering to begin
> > maintaining the parport drivers. I have spent some time studying the
> > drivers closely, and I've read Love's book linux kernel development, so
> > I think I'm just about ready for this.
> >
> > My question is; what are some of the outstanding issues with parport
> > which people would like to see addressed?
>
> There are probably others, but "Advanced Search" at
> bugzilla.kernel.org finds these 4 bug reports:
>...
You don't need an advanced search.
There's a component Drivers/Parallel in the kernel Bugzilla that
contains a superset of the bugs from your search.
> ~Randy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-07-17 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 16:09 maintainer: parport drivers Mike Sharkey
2007-07-17 16:58 ` Randy Dunlap
2007-07-17 17:12 ` Adrian Bunk [this message]
2007-07-17 20:47 ` Rene Herman
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=20070717171236.GG3801@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@pikeaero.com \
--cc=randy.dunlap@oracle.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