From: Greg KH <greg@kroah.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for January 6 (staging/android #2)
Date: Tue, 6 Jan 2009 16:53:24 -0800 [thread overview]
Message-ID: <20090107005324.GA3606@kroah.com> (raw)
In-Reply-To: <20090106163931.5c275833.randy.dunlap@oracle.com>
On Tue, Jan 06, 2009 at 04:39:31PM -0800, Randy Dunlap wrote:
> On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
> >
> > Changes since 20090105:
> >
> > New tree:
> > squashfs
> >
> > Undropped tree:
> > usb
> > staging
>
>
> drivers/staging/android/timed_gpio.c:21:27: error: asm/arch/gpio.h: No such file or directory
Crap, this is an ARM specific thing :(
I'll fix this up after dinner...
thanks,
greg k-h
prev parent reply other threads:[~2009-01-07 0:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 7:23 linux-next: Tree for January 6 Stephen Rothwell
2009-01-06 16:29 ` linux-next: Tree for January 6 (MTD) Randy Dunlap
2009-01-06 17:36 ` Alexey Korolev
2009-01-06 21:16 ` Randy Dunlap
2009-01-09 21:48 ` Randy Dunlap
2009-01-06 21:23 ` linux-next: Tree for January 6 (wimax errs) Randy Dunlap
2009-01-06 21:50 ` Iñaky Pérez-González
2009-01-07 8:09 ` Inaky Perez-Gonzalez
2009-01-07 0:25 ` linux-next: Tree for January 6 (staging/altpciehdma) Randy Dunlap
2009-01-07 0:26 ` linux-next: Tree for January 6 (staging/comedi) Randy Dunlap
2009-01-07 0:35 ` linux-next: Tree for January 6 (staging/meilhaus) Randy Dunlap
2009-01-07 0:37 ` linux-next: Tree for January 6 (staging/android) Randy Dunlap
2009-01-07 0:39 ` linux-next: Tree for January 6 (staging/android #2) Randy Dunlap
2009-01-07 0:53 ` Greg KH [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=20090107005324.GA3606@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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