public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Craig Milo Rogers <rogers@isi.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: Termination of the Philips Webcam Driver (pwc)
Date: Fri, 27 Aug 2004 09:43:46 +0100	[thread overview]
Message-ID: <20040827094346.B29407@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0408261700320.2304@ppc970.osdl.org>; from torvalds@osdl.org on Thu, Aug 26, 2004 at 05:03:42PM -0700

On Thu, Aug 26, 2004 at 05:03:42PM -0700, Linus Torvalds wrote:
> Of course if some new maintainer shows up and decides to infer how the 
> device worked by looking at the original open-source code, that's also 
> clearly fine.
> 
> I don't want people to play lawyer. Honoring peoples rights to the code 
> they write is more important than just the law.

Umm, just because he's piised off we shouldn't removed support for hardware.
it's not like the driver suddenly stops from working because it's unmaintained.


  reply	other threads:[~2004-08-27  8:44 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 23:32 Termination of the Philips Webcam Driver (pwc) Craig Milo Rogers
2004-08-26 23:47 ` Christoph Hellwig
2004-08-27  0:03   ` Linus Torvalds
2004-08-27  8:43     ` Christoph Hellwig [this message]
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 21:59                 ` non-i386 architectures (Re: Termination of the Philips Webcam Driver (pwc)) Daniel Egger
2004-08-27 19:06               ` Termination of the Philips Webcam Driver (pwc) 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
  -- 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-28  2:16 lkml-mail
2004-08-28  5:30 ` Greg KH

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=20040827094346.B29407@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rogers@isi.edu \
    --cc=torvalds@osdl.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