All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ryan Hope <rmh3093@gmail.com>, Dave Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, dri-devel@lists.sf.net
Subject: Re: [git pull] drm - fixes + radeon KMS (part 2)
Date: Tue, 16 Jun 2009 14:03:09 -0700	[thread overview]
Message-ID: <20090616210309.GA3563@kroah.com> (raw)
In-Reply-To: <21d7e9970906161356y75702185gff0500571fff1e47@mail.gmail.com>

On Wed, Jun 17, 2009 at 06:56:31AM +1000, Dave Airlie wrote:
> On Wed, Jun 17, 2009 at 6:52 AM, Linus
> Torvalds<torvalds@linux-foundation.org> wrote:
> >
> >
> > On Wed, 17 Jun 2009, Dave Airlie wrote:
> >>
> >> Linus can you pull this tree?
> >
> > I hate pulling trees when I know there are _known_ bugs.
> >
> > Even during the merge window. The rest of the -rc series is for fixing up
> > bugs, yes, but not bugs that were introduced on purpose.
> >
> 
> It only happens if the user enable staging drivers, and I suspect staging
> has much worse bugs, but okay I'll put the initcall fix into the tree
> and send you another pull request.

Note, distros enable the staging tree to pick up drivers they were
previously including anyway.  So that is quite a large userbase :)

thanks,

greg k-h

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15  2:08 [git pull] drm - fixes + radeon KMS (part 2) Dave Airlie
2009-06-15  2:22 ` Greg KH
2009-06-15  2:43   ` Dave Airlie
2009-06-16 15:53     ` Ryan Hope
2009-06-16 18:20       ` Linus Torvalds
2009-06-16 20:45         ` Dave Airlie
2009-06-16 20:52           ` Linus Torvalds
2009-06-16 20:56             ` Dave Airlie
2009-06-16 21:03               ` Greg KH [this message]
2009-06-16 18:45     ` 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=20090616210309.GA3563@kroah.com \
    --to=greg@kroah.com \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmh3093@gmail.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.