From: Pete Zaitcev <zaitcev@redhat.com>
To: john@antefacto.com, linux-kernel@vger.kernel.org
Subject: Re: Etiquette of getting a driver into the kernel
Date: Sat, 24 Nov 2001 13:46:08 -0500 [thread overview]
Message-ID: <200111241846.fAOIk8B01067@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1006511470.4667.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.1006511470.4667.linux-kernel2news@redhat.com>
>[...] 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 :)
You must resolve the licensing issue first. Once you are
done, send it to linux-usb-devel@lists.sourceforge.net.
The USB subsystem has an active maintainer currently.
-- Pete
next parent reply other threads:[~2001-11-24 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1006511470.4667.linux-kernel2news@redhat.com>
2001-11-24 18:46 ` Pete Zaitcev [this message]
2001-11-26 9:47 ` Etiquette of getting a driver into the kernel John P. Looney
2001-11-23 10:28 John P. Looney
2001-11-23 21:38 ` bert hubert
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=200111241846.fAOIk8B01067@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=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.