From: Richard Weinberger <richard@nod.at>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Daniel Walter <dwalter@google.com>
Subject: Re: linux-next: Tree for Sep 30 (uml)
Date: Tue, 30 Sep 2014 20:59:22 +0200 [thread overview]
Message-ID: <542AFD8A.8060806@nod.at> (raw)
In-Reply-To: <542AFB5E.7040308@infradead.org>
Am 30.09.2014 20:50, schrieb Randy Dunlap:
> On 09/30/14 03:12, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20140926:
>>
>
> uml defconfig on i386 and x86_64:
>
> In file included from ../arch/x86/um/asm/processor.h:31:0,
> from ../arch/um/include/asm/uaccess.h:16,
> from ../arch/um/include/asm/thread_info.h:13,
> from ../include/linux/thread_info.h:54,
> from ../include/asm-generic/current.h:4,
> from arch/um/include/generated/asm/current.h:1,
> from ../include/linux/mutex.h:13,
> from ../include/linux/kernfs.h:13,
> from ../include/linux/sysfs.h:15,
> from ../include/linux/kobject.h:21,
> from ../include/linux/device.h:17,
> from ../include/linux/platform_device.h:14,
> from ../drivers/base/platform.c:14:
> ../arch/um/include/asm/processor-generic.h:107:19: error: expected identifier or '(' before '&' token
> #define cpu_data (&boot_cpu_data)
> ^
> ../include/linux/pm_domain.h:74:23: note: in expansion of macro 'cpu_data'
> struct gpd_cpu_data *cpu_data;
Thank you Randy, will look into this tomorrow.
Thanks,
//richard
next prev parent reply other threads:[~2014-09-30 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 10:12 linux-next: Tree for Sep 30 Stephen Rothwell
2014-09-30 16:26 ` Guenter Roeck
2014-09-30 19:36 ` [PATCH linux-next] clk-gpio-gate: include gpio/consumer to fix build Vincent Stehlé
2014-09-30 21:27 ` Mike Turquette
2014-09-30 18:50 ` linux-next: Tree for Sep 30 (uml) Randy Dunlap
2014-09-30 18:59 ` Richard Weinberger [this message]
2014-10-01 7:22 ` Geert Uytterhoeven
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=542AFD8A.8060806@nod.at \
--to=richard@nod.at \
--cc=dwalter@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).