From: Ingo Molnar <mingo@elte•hu>
To: Greg KH <greg@kroah•com>
Cc: Peter Zijlstra <a.p.zijlstra@chello•nl>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: How linux-staging is released (was Re: linux-staging/linux-next merge/build errors)
Date: Thu, 26 Jun 2008 14:30:09 +0200 [thread overview]
Message-ID: <20080626123009.GO29619@elte.hu> (raw)
In-Reply-To: <20080621215059.GD15341@kroah.com>
* Greg KH <greg@kroah•com> wrote:
> On Sat, Jun 21, 2008 at 08:02:22PM +0200, Peter Zijlstra wrote:
> > The point was that for some people being carried by distos is upstream
> > enough.
> >
> > So I would discourage distros form picking up this tree.
>
> I wouldn't, as some of the drivers work just fine on some arches, but
> not all, that is why they are not in mainline yet (the network drivers
> in there right now are an example of this.)
.. and it's all source code, so it's not really different to distros
than a number of other patches they regularly pick up. If there's too
much mess there's always the option to look into the fine source code
and fix things up.
If a driver ended up not mattering at all in the long run then nobody
will ever fix it up - and we dont even care that much - it's almost as
if it didnt even exist.
The other alternative is much more harmful: vendors release binary-only
drivers. That only works on x86 and they are utterly unfixable as well
and have a lot of other disadvantages.
So we really have to balance the natural desire for pure upstream
drivers against the real dangers of vendors doing bin-only modules just
for the convenience of distribution.
... all in one: kudos Greg for doing the linux-staging tree! :-) It will
help a lot.
Ingo
prev parent reply other threads:[~2008-06-26 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 2:40 linux-staging/linux-next merge/build errors Stephen Rothwell
2008-06-21 7:10 ` Greg KH
2008-06-21 7:19 ` How linux-staging is released (was Re: linux-staging/linux-next merge/build errors) Greg KH
2008-06-21 13:00 ` Peter Zijlstra
2008-06-21 17:50 ` Greg KH
2008-06-21 18:02 ` Peter Zijlstra
2008-06-21 21:50 ` Greg KH
2008-06-26 12:30 ` Ingo Molnar [this message]
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=20080626123009.GO29619@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=a.p.zijlstra@chello$(echo .)nl \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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