All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John P. Looney" <john@antefacto.com>
To: linux-kernel@vger.kernel.org
Subject: Etiquette of getting a driver into the kernel
Date: Fri, 23 Nov 2001 10:28:28 +0000	[thread overview]
Message-ID: <20011123102828.D27980@antefacto.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 969 bytes --]

 I've a Phison "usb multiple card reader". Nice little device, though I
think the driver isn't the best (block size of 1k when reading & writing
gets 80k/sec, block size of 32k gets 850k/sec).

 The device came with a driver for linux on a floppy, as a patch against
2.4.2. It needed a little beating to get it to compile, and it caused
not-a-few kernel panics. Some kind soul on the net mailed me a newer
version, which does work a lot more reliably. The email address given for
the original author (in the source) doesn't seem to answer requests like
"is there a newer version of this driver", or "Is this driver GPL'd ?".

 Basically, I've a patch for it against 2.4.15, and I'm wondering how I
should go about getting it into the kernel, so others can debug it for me :)

John

-- 
_______________________________________
John Looney             Chief Scientist
a n t e f a c t o     t: +353 1 8586004
www.antefacto.com     f: +353 1 8586014


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2001-11-23 10:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 10:28 John P. Looney [this message]
2001-11-23 21:38 ` Etiquette of getting a driver into the kernel bert hubert
     [not found] <mailman.1006511470.4667.linux-kernel2news@redhat.com>
2001-11-24 18:46 ` Pete Zaitcev
2001-11-26  9:47   ` John P. Looney

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=20011123102828.D27980@antefacto.com \
    --to=john@antefacto.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 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.