public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [GIT PATCH] STAGING patches for .39
Date: Wed, 16 Mar 2011 17:28:18 -0700	[thread overview]
Message-ID: <20110317002818.GA19812@kroah.com> (raw)
In-Reply-To: <AANLkTim13aZ0Mr5RrOeQizHGY3jhf97x8v9mznY8RqgE@mail.gmail.com>

On Wed, Mar 16, 2011 at 05:19:47PM -0700, Linus Torvalds wrote:
> On Wed, Mar 16, 2011 at 2:03 PM, Greg KH <greg@kroah.com> wrote:
> > Here is the big staging tree merge for .39
> 
> So I try to compile all the staging drivers every once in a while.
> 
> This time I gave up even trying. After the GMA500 driver didn't
> compile (due to some crazy patch to dri_pci_init() that changes it to
> a calling convention that it has never had), there was another file
> that spewed out about five thousand lines of error/warning messages.
> 
> Aren't those things supposed to at least compile? What's going on?

The gma500 driver will not build until you pull the drm tree into yours
as that is an api dependancy it needs.  I didn't think you build staging
drivers, so I didn't think I needed to call this one out.  I was wrong :)

As for the others, I don't know of any build problems, what one did you
have a problem with?

thanks,

greg k-h

  reply	other threads:[~2011-03-17  0:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 21:03 [GIT PATCH] STAGING patches for .39 Greg KH
     [not found] ` <1300309804-3756-1-git-send-email-gregkh@suse.de>
2011-03-16 21:03   ` [PATCH 584/961] staging: brcm80211: Fix memory leak after kmalloc failure Greg Kroah-Hartman
2011-03-17  0:19 ` [GIT PATCH] STAGING patches for .39 Linus Torvalds
2011-03-17  0:28   ` Greg KH [this message]
2011-03-17  0:32     ` Linus Torvalds
2011-03-17  0:34       ` Linus Torvalds
2011-03-17  1:52         ` Greg KH
2011-03-17  2:02           ` Greg KH
2011-03-17 19:55             ` Randy Dunlap
2011-03-17 20:04               ` Greg KH
2011-03-17 20:17                 ` Randy Dunlap
2011-03-17  1:51       ` 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=20110317002818.GA19812@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox