public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Ben Collins <ben.collins@ubuntu.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/15] Ubuntu patch sync
Date: Wed, 4 Jan 2006 22:15:17 -0500	[thread overview]
Message-ID: <20060105031517.GD2658@redhat.com> (raw)
In-Reply-To: <20060104150658.5b3f0d20@dxpl.pdx.osdl.net>

On Wed, Jan 04, 2006 at 03:06:58PM -0800, Stephen Hemminger wrote:

 > > 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.
 > 
 > I don't mean to play shoot the messenger, you are helping a lot by doing this
 > I wish every distro did.

FWIW, Red Hat has been under constant pressure from users asking us
to merge driver x 'because $otherdistro has it' for a long time.

The first reason we say no 99.9% of the time is because to stay in
a position where we can quickly rebase to a new upstream release, you 
have to be light enough to not have to spend a day rediffing/fixing
add-on patches.

The second reason (and this is actually more important than the first,
but as I'm a selfish sod, I thought of my own wellbeing first), is that
historically there have been some vendors who have taken the position
"Our driver is in Red Hat's distro, we don't care about anyone else".
For obvious reasons, this isn't a good thing, and something we now
go out of our way to discourage.

>From time to time, we do carry drivers that aren't upstream yet.
ipw2x00 got a good beating in RHEL4 & FC3 before it made it into Linus' tree.
A lot of issues were found in that driver early on by rhel beta-testers,
which Intel went and fixed, long before it was proposed for upstream inclusion.
Whilst some of those issues would probably have been found by -mm exposure
eventually, living in a distro tree gets it a lot more exposure.

Getting 'previews' of drivers into the grubby hands of end-users
who are prepared for a bumpy ride, and are prepared to give feedback
to improve things is invaluable.

For Fedora at least, I don't object to the notion of carrying a handful
of continually improving drivers which are making progress at upstream
inclusion.  What I don't want to entertain is the idea of grabbing
random drivers and dumping them in the distro tree just because their
upstream has no motivation at getting them merged in Linus' tree.
(Which is sadly a category quite a few of the requests that we get
 fall into)

		Dave


  reply	other threads:[~2006-01-05  3:15 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
2006-01-04 23:06         ` Stephen Hemminger
2006-01-05  3:15           ` Dave Jones [this message]
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=20060105031517.GD2658@redhat.com \
    --to=davej@redhat.com \
    --cc=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