public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Adrian Bunk <bunk@stusta.de>, Dan Dennedy <dan@dennedy.org>,
	Ben Collins <bcollins@debian.org>,
	Linux1394-Devel <linux1394-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's
Date: Tue, 21 Dec 2004 09:27:46 -0800	[thread overview]
Message-ID: <20041221172746.GI1459@kroah.com> (raw)
In-Reply-To: <1103649633.9220.12.camel@krustophenia.net>

On Tue, Dec 21, 2004 at 12:20:32PM -0500, Lee Revell wrote:
> On Tue, 2004-12-21 at 09:17 -0800, Greg KH wrote:
> > On Mon, Dec 20, 2004 at 05:58:06PM -0500, Lee Revell wrote:
> > > On Mon, 2004-12-20 at 23:53 +0100, Adrian Bunk wrote:
> > > > The solution is simple:
> > > > The vendor or services provider submits his driver for inclusion into 
> > > > the kernel which is the best solution for everyone.
> > > > 
> > > 
> > > What if the driver is under development and doesn't work yet?
> > 
> > Many drivers have been accepted into the kernel tree before they worked
> > properly :)
> 
> Yeah but I hope you can understand why someone would be hesitant to
> submit a broken driver.  It just makes the author look bad.  I would not
> feel right submitting something that didn't work.

Everyone has their own comfort levels :)

Anyway, a number of drivers have been submitted to the tree that were
never even tested on hardware (written only to specs).  Then, over time
they were properly debugged by people who had access to the hardware
(debugging over email does have long lags, but it works out in the end.)
An example of this was the first usb bluetooth driver.

But we are getting pretty far off-topic here, sorry.

greg k-h

  reply	other threads:[~2004-12-21 17:29 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20  1:53 [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's Adrian Bunk
2004-12-20  2:10 ` Dan Dennedy
2004-12-20  2:25   ` Adrian Bunk
2004-12-20  2:42     ` Lee Revell
2004-12-20  4:27       ` Dan Dennedy
2004-12-20 22:53         ` Adrian Bunk
2004-12-20 22:58           ` Lee Revell
2004-12-20 23:02             ` Adrian Bunk
2004-12-20 23:21               ` Lee Revell
2004-12-21  0:40               ` Alan Cox
2004-12-21 17:17             ` Greg KH
2004-12-21 17:20               ` Lee Revell
2004-12-21 17:27                 ` Greg KH [this message]
2004-12-21 22:19                 ` Theodore Ts'o
2004-12-22 14:08                   ` Alan Cox
2004-12-20  9:01 ` Arne Caspari
2004-12-20 12:15   ` Arjan van de Ven
2004-12-20 13:20     ` Arne Caspari
2004-12-20 14:35       ` Alan Cox
2004-12-22  8:29       ` Arjan van de Ven
2004-12-22  8:57         ` Stefan Richter
2004-12-22 12:01           ` Christoph Hellwig
2004-12-22 12:21             ` Arne Caspari
2004-12-22 16:04             ` Stefan Richter
2004-12-20 14:39   ` Ben Collins
2004-12-20 15:15     ` Alan Cox
2004-12-20 15:46       ` Ben Collins
2004-12-20 20:15         ` Alan Cox
2004-12-21  8:33           ` Arne Caspari
2004-12-21 12:00             ` Adrian Bunk
2004-12-21 12:49               ` Arne Caspari
2004-12-21 17:15                 ` Greg KH
2004-12-21 18:51                   ` Arne Caspari
2004-12-21 18:58                     ` Greg KH
2004-12-20 17:51   ` Adrian Bunk
2004-12-20 21:05     ` Lee Revell
2004-12-20 21:49       ` girish wadhwani
2004-12-21  8:37         ` Arne Caspari
2004-12-21  9:06           ` Bernard Leach
2004-12-21 23:35         ` Pieter Palmers
2004-12-22  0:56           ` Lee Revell
2004-12-21  0:42     ` updated: " Adrian Bunk
2004-12-21  8:46       ` Arne Caspari
2004-12-21 17:13         ` 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=20041221172746.GI1459@kroah.com \
    --to=greg@kroah.com \
    --cc=bcollins@debian.org \
    --cc=bunk@stusta.de \
    --cc=dan@dennedy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=rlrevell@joe-job.com \
    /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