public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lubomir Rintel <lkundrak@v3.sk>
To: Dave Airlie <airlied@gmail.com>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: The Linux Staging tree, what it is and is not.
Date: Fri, 20 Mar 2009 17:05:58 +0100	[thread overview]
Message-ID: <1237565158.32737.11.camel@localhost.localdomain> (raw)
In-Reply-To: <21d7e9970903192126r69687891madbce3d5ee77f6a0@mail.gmail.com>

On Fri, 2009-03-20 at 14:26 +1000, Dave Airlie wrote:
> Staging doesn't fulfill this role from my POV:
> a) what sane distro will enable staging drivers? do they care about their users?

If the code there actually builds, I don't see a problem with packaging
the staging drivers into a -crap subpackage, or maybe blacklisting them
all by default, but saving the user who wants to cut his head off and
watch himself bleed from having to recompile the kernel package for
that.

-- 
Lubomir Rintel <lkundrak@v3.sk>


      parent reply	other threads:[~2009-03-20 16:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 18:32 The Linux Staging tree, what it is and is not Greg KH
2009-03-20  0:58 ` Robert Schwebel
2009-03-20  2:48   ` Greg KH
2009-03-20  8:34     ` Daniel Krüger
2009-03-20  8:46       ` Robert Schwebel
2009-03-20 17:25       ` Greg KH
2009-03-20 10:01   ` Alan Cox
2009-03-20 10:35     ` Robert Schwebel
2009-03-20 10:55       ` Alan Cox
2009-03-20 11:15         ` Robert Schwebel
2009-03-20 15:16           ` Daniel Krüger
2009-03-20 15:37             ` Alan Cox
2009-03-20 20:32               ` david
2009-03-23  9:03                 ` Daniel Krüger
2009-03-23  9:16                   ` Robert Schwebel
2009-03-20  4:26 ` Dave Airlie
2009-03-20  4:46   ` Greg KH
2009-03-20 16:05   ` Lubomir Rintel [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=1237565158.32737.11.camel@localhost.localdomain \
    --to=lkundrak@v3.sk \
    --cc=airlied@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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