From: "Mike Sharkey" <mike@pikeaero.com>
To: linux-kernel@vger.kernel.org
Subject: maintainer: parport drivers
Date: Tue, 17 Jul 2007 12:09:16 -0400 [thread overview]
Message-ID: <1184688556.711.8.camel@jake> (raw)
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?
Kind Regards,
Mike Sharkey
Pike Aerospace Research Corporation
Bradford, Ontario
Canada
http://www.pikeaero.com
next reply other threads:[~2007-07-17 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 16:09 Mike Sharkey [this message]
2007-07-17 16:58 ` maintainer: parport drivers Randy Dunlap
2007-07-17 17:12 ` Adrian Bunk
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=1184688556.711.8.camel@jake \
--to=mike@pikeaero.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox