From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: kbuild tree build failure
Date: Wed, 3 Dec 2008 10:46:58 +0100 [thread overview]
Message-ID: <20081203094658.GA2030@uranus.ravnborg.org> (raw)
In-Reply-To: <20081203113650.d4245a05.sfr@canb.auug.org.au>
On Wed, Dec 03, 2008 at 11:36:50AM +1100, Stephen Rothwell wrote:
> Hi Sam,
>
> On Wed, 26 Nov 2008 22:06:57 +0100 Sam Ravnborg <sam@ravnborg.org> wrote:
> >
> > On Wed, Nov 26, 2008 at 03:42:06PM +1100, Stephen Rothwell wrote:
> > > Hi Sam,
> > >
> > > Today's linux-next build (x86_64 allmodconfig) failed like this:
> > >
> > > In file included from arch/x86/include/asm/processor.h:15,
> > > from include/linux/prefetch.h:14,
> > > from include/linux/list.h:6,
> > > from include/linux/module.h:9,
> > > from kernel/configs.mod.c:1:
> > > arch/x86/include/asm/current.h:23: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'struct'
> > >
> > > and went rapidly down hill from there.
> >
> > I will cook up a fix tomorrow if day-time job does not become night-time.
>
> I am still getting the same errors ...
I have been concentrating (used all my spare time) on sparc unification.
Will fix this soonish.
I need to reshuffle a few patches nothing major. But it will
take me a few hours.
Sam
next prev parent reply other threads:[~2008-12-03 9:47 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 4:42 linux-next: kbuild tree build failure Stephen Rothwell
2008-11-26 21:06 ` Sam Ravnborg
2008-11-26 23:49 ` Stephen Rothwell
2008-12-03 0:36 ` Stephen Rothwell
2008-12-03 9:46 ` Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-14 1:20 Stephen Rothwell
2009-10-14 7:43 ` Sam Ravnborg
2009-06-09 1:48 Stephen Rothwell
2009-06-09 16:15 ` Sam Ravnborg
2009-06-09 16:19 ` Stephen Rothwell
2009-06-09 21:04 ` Sam Ravnborg
2009-06-09 23:27 ` Stephen Rothwell
2009-05-05 1:17 Stephen Rothwell
2009-05-05 6:35 ` Jan Beulich
2009-05-05 6:43 ` Sam Ravnborg
2009-05-05 7:04 ` Jan Beulich
2008-11-25 4:47 Stephen Rothwell
2008-11-25 8:42 ` Sam Ravnborg
2008-11-25 8:58 ` Stephen Rothwell
2008-07-12 22:32 Milton Miller
2008-07-12 22:32 ` Milton Miller
2008-07-12 23:21 ` Roman Zippel
2008-07-12 23:21 ` Roman Zippel
2008-07-07 8:40 Stephen Rothwell
2008-07-07 8:40 ` Stephen Rothwell
2008-07-07 12:51 ` Sam Ravnborg
2008-07-07 12:51 ` Sam Ravnborg
2008-07-07 13:08 ` Stephen Rothwell
2008-07-07 13:08 ` Stephen Rothwell
2008-07-07 16:13 ` Roman Zippel
2008-07-07 16:13 ` Roman Zippel
2008-07-07 21:01 ` Sam Ravnborg
2008-07-07 23:36 ` Michael Ellerman
2008-07-07 23:36 ` Michael Ellerman
2008-07-08 2:55 ` Roman Zippel
2008-07-08 2:55 ` Roman Zippel
2008-07-10 0:51 ` Michael Ellerman
2008-07-10 0:51 ` Michael Ellerman
2008-07-10 14:59 ` Roman Zippel
2008-07-10 14:59 ` Roman Zippel
2008-07-14 16:53 ` Milton Miller
2008-07-14 16:53 ` Milton Miller
2008-07-08 21:19 ` Sam Ravnborg
2008-07-10 14:52 ` Roman Zippel
2008-07-25 4:13 ` Stephen Rothwell
2008-07-25 4:13 ` Stephen Rothwell
2008-07-26 10:06 ` Sam Ravnborg
2008-07-26 10:06 ` Sam Ravnborg
2008-07-26 12:40 ` Stephen Rothwell
2008-07-26 12:40 ` Stephen Rothwell
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=20081203094658.GA2030@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-next@vger.kernel.org \
--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 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.