public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <ben.collins@ubuntu.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/15] Ubuntu patch sync
Date: Wed, 04 Jan 2006 17:45:39 -0500	[thread overview]
Message-ID: <1136414740.4430.44.camel@grayson> (raw)
In-Reply-To: <20060104143023.5b2f7967@dxpl.pdx.osdl.net>

On Wed, 2006-01-04 at 14:30 -0800, Stephen Hemminger wrote:
> On Wed, 04 Jan 2006 17:12:48 -0500
> Ben Collins <ben.collins@ubuntu.com> wrote:
> 
> > On Wed, 2006-01-04 at 14:06 -0800, Stephen Hemminger wrote:
> > > On Wed, 04 Jan 2006 16:59:02 -0500
> > > Ben Collins <bcollins@ubuntu.com> wrote:
> > > 
> > > > These patches are just attempts to merge code from the ubuntu kernel tree.
> > > > This is most of the differences between our tree and stock code (not
> > > > necessarily all differences, since we do have a lot of external drivers
> > > > pulled in).
> > > 
> > > Why not submit them too?
> > 
> > Because neither I nor Ubuntu maintains them as upstream. I would rather
> > leave it to the upstream authors of those drivers (e.g. rt2400, rt2500,
> > unionfs, etc.) to submit their own code to Linus.
> > 
> 
> Just want to needle the upstream drivers to submit and get reviewed.

After dealing with literally dozens of upstream drivers, I think the
reasons boil down to a few categories:

1 - They know their code is crappy and they don't want to deal with code
review.

2 - They want to retain total control of their code. Having it in the
kernel tree means that the driver can be modified by others (in usually
correct ways) without their consent. They don't want to have to track
these changes and accommodate them. Also, external drivers tend to
retain a lot of backward compatibility for older kernel versions, that
would surely be dropped if it was placed in the kernel proper.

3 - They don't think their driver is important enough. They have a small
user base, and deal directly with those users.

4 - They just don't know how.

Not defending any of these reasons. I'd love to not have all this work
of pulling in and tracking the drivers that our users need/want, but
it's going to be a lot of work. Maybe I'll start emailing them about
getting their code in the kernel tree.

-- 
   Ben Collins <ben.collins@ubuntu.com>
   Developer
   Ubuntu Linux


  reply	other threads:[~2006-01-04 22:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 21:59 [PATCH 0/15] Ubuntu patch sync Ben Collins
2006-01-04 22:06 ` Stephen Hemminger
2006-01-04 22:12   ` Ben Collins
2006-01-04 22:30     ` Stephen Hemminger
2006-01-04 22:45       ` Ben Collins [this message]
2006-01-04 23:06         ` Stephen Hemminger
2006-01-05  3:15           ` Dave Jones
2006-01-05 15:46         ` David Woodhouse
2006-01-05 15:54           ` Ben Collins
2006-01-05  7:53     ` Jan Engelhardt
2006-01-05 18:52       ` Francois Romieu
2006-01-05 19:40         ` Dominik Brodowski
2006-01-04 22:40 ` Paolo Ciarrocchi
  -- strict thread matches above, loose matches on Subject: below --
2006-02-01 20:07 Brown, Len

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=1136414740.4430.44.camel@grayson \
    --to=ben.collins@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@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