From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Vineet Gupta <vgupta@synopsys.com>,
Peter Hurley <peter@hurleysoftware.com>
Subject: Re: linux-next: Tree for Feb 3 (arc:defconfig build failure)
Date: Tue, 3 Feb 2015 10:42:18 -0800 [thread overview]
Message-ID: <20150203184218.GA20822@roeck-us.net> (raw)
In-Reply-To: <20150203182010.73624992@canb.auug.org.au>
On Tue, Feb 03, 2015 at 06:20:10PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150202:
>
> The target-updates tree gained a conflict against Linus' tree.
>
> The clk tree gained conflicts against the arm-soc tree.
>
> Non-merge commits (relative to Linus' tree): 7173
> 7143 files changed, 301126 insertions(+), 167764 deletions(-)
>
> ----------------------------------------------------------------------------
>
Building arc:defconfig ... failed
--------------
Error log:
drivers/built-in.o: In function `of_setup_earlycon':
(.init.text+0xb3e): undefined reference to `arc_early_base_baud'
drivers/built-in.o: In function `setup_earlycon':
(.init.text+0xcd0): undefined reference to `arc_early_base_baud'
make: *** [vmlinux] Error 1
This is due to "ARC: Dynamically determine BASE_BAUD from DeviceTree".
arc:defconfig does not define CONFIG_SERIAL_8250 and thus also not
CONFIG_SERIAL_8250_CONSOLE, but it looks like it is mandatory
after this patch.
Guenter
next prev parent reply other threads:[~2015-02-03 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 7:20 linux-next: Tree for Feb 3 Stephen Rothwell
2015-02-03 18:42 ` Guenter Roeck [this message]
2015-02-03 19:07 ` linux-next: Tree for Feb 3 (arc:defconfig build failure) Peter Hurley
2015-02-03 21:11 ` Guenter Roeck
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=20150203184218.GA20822@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=sfr@canb.auug.org.au \
--cc=vgupta@synopsys.com \
/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.