From: Greg KH <greg@kroah.com>
To: lkml-mail@asthe.com, random-mail@LavaRnd.org
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: Termination of the Philips Webcam Driver (pwc)
Date: Fri, 27 Aug 2004 22:30:12 -0700 [thread overview]
Message-ID: <20040828053012.GD10151@kroah.com> (raw)
In-Reply-To: <74c68b63c43337d4366c367b282f4b91916d61ff@asthe.com>
On Fri, Aug 27, 2004 at 07:16:18PM -0700, lkml-mail@asthe.com wrote:
>
> We would be happy to discuss ways that the pwc might be maintained
> in the linux kernel. If we can help, please ask us (see
> http://www.lavarnd.org/about-us/contact-us.html for our EMail address).
Great. Here's what you can do. Take the patch availble at:
http://linux.bkbits.net:8080/linux-2.5/cset@412d8e0cqutBsdGubqorXXCeHHdS2g
and apply it reversed to your kernel tree (with -R as an option to
patch). That patch has the binary hook already removed.
Then clean up the text a bit to point to you as the maintainer, that no
one should bother the original author anymore, and such. Cleanup and
change anything else that you think needs to be done to the driver, and
then send me that patch as documented in the
Documentation/SubmittingPatches in the kernel tree.
Then you would be the new maintainer of the driver, and the code would
be back in the kernel tree.
Sound good?
thanks,
greg k-h
next prev parent reply other threads:[~2004-08-28 5:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 2:16 Termination of the Philips Webcam Driver (pwc) lkml-mail
2004-08-28 5:30 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-27 10:14 Koos Vriezen
2004-08-27 11:03 ` Marcus Metzler
2004-08-26 23:32 Craig Milo Rogers
2004-08-26 23:47 ` Christoph Hellwig
2004-08-27 0:03 ` Linus Torvalds
2004-08-27 8:43 ` Christoph Hellwig
2004-08-27 9:48 ` Craig Milo Rogers
2004-08-27 17:28 ` Linus Torvalds
2004-08-27 17:37 ` Xavier Bestel
2004-08-27 18:13 ` Linus Torvalds
2004-08-27 18:55 ` Craig Milo Rogers
2004-08-27 19:06 ` Linus Torvalds
2004-08-27 19:34 ` Jeff Garzik
2004-08-27 21:42 ` Nemosoft Unv.
2004-08-27 22:49 ` Marek Habersack
2004-08-27 23:40 ` Dmitry Torokhov
2004-08-28 17:42 ` Pavel Machek
2004-08-27 23:04 ` Craig Milo Rogers
2004-08-27 19:06 ` Martin J. Bligh
2004-08-27 19:12 ` Alex Belits
2004-08-27 21:36 ` Anton Altaparmakov
2004-08-27 21:42 ` Anton Altaparmakov
2004-08-27 22:26 ` Geert Uytterhoeven
2004-08-27 21:52 ` Linus Torvalds
2004-08-27 22:22 ` Jeff Garzik
2004-08-28 0:45 ` Paul Jakma
2004-08-28 0:53 ` Craig Milo Rogers
2004-08-28 10:29 ` Norbert van Nobelen
2004-08-29 14:37 ` Alan Cox
2004-08-28 9:26 ` chris
2004-08-29 14:41 ` Alan Cox
2004-08-29 14:36 ` Alan Cox
2004-08-29 18:09 ` Linus Torvalds
2004-08-29 18:57 ` Alan Cox
2004-08-29 19:40 ` Greg KH
2004-08-30 9:35 ` Craig Milo Rogers
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=20040828053012.GD10151@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=lkml-mail@asthe.com \
--cc=random-mail@LavaRnd.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