From: "Iñaky Pérez-González" <inaky.perez-gonzalez@intel•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>,
linux-wimax@intel•com, wimax@linuxwimax•org
Subject: Re: linux-next: Tree for January 6 (wimax errs)
Date: Tue, 6 Jan 2009 13:50:02 -0800 [thread overview]
Message-ID: <200901061350.02562.inaky.perez-gonzalez@intel.com> (raw)
In-Reply-To: <20090106132321.8a330942.randy.dunlap@oracle.com>
On Tuesday 06 January 2009, 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:
>
> wimax build fails when CONFIG_INPUT=n:
Ops -- my fault -- working on a fix.
> Also, this warning needs to be fixed:
>
> linux-next-20090106/net/wimax/id-table.c:133: warning: ISO C90 forbids
> mixed declarations and code
Will fix too.
Thanks Randy,
next prev parent reply other threads:[~2009-01-06 21:50 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 [this message]
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
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=200901061350.02562.inaky.perez-gonzalez@intel.com \
--to=inaky.perez-gonzalez@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wimax@intel$(echo .)com \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=wimax@linuxwimax$(echo .)org \
/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