From: Catalin Marinas <catalin.marinas@arm.com>
To: Chen Gang <gang.chen@asianux.com>
Cc: Will Deacon <Will.Deacon@arm.com>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"anup.patel@linaro.org" <anup.patel@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggestion] ARM64:kernel: compiling issue for early_console.
Date: Wed, 27 Mar 2013 11:55:09 +0000 [thread overview]
Message-ID: <20130327115509.GA1603@MacBook-Pro.local> (raw)
In-Reply-To: <5152DB83.8080703@asianux.com>
On Wed, Mar 27, 2013 at 11:44:03AM +0000, Chen Gang wrote:
> the error message:
> arch/arm64/kernel/early_printk.c: At top level:
> arch/arm64/kernel/early_printk.c:98:23: error: conflicting types for ‘early_console’
> In file included from arch/arm64/kernel/early_printk.c:20:0:
> include/linux/console.h:145:24: note: previous declaration of ‘early_console’ was here
> make[1]: *** [arch/arm64/kernel/early_printk.o] Error 1
> make: *** [arch/arm64/kernel] Error 2
Is this in linux-next? Mainline seems fine.
I saw some patches from tglx on unifying the various early printk
implementations, though not sure whether it's those patches causing it
(in which case arm64 needs to be updated as well).
--
Catalin
next prev parent reply other threads:[~2013-03-27 11:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 11:44 [Suggestion] ARM64:kernel: compiling issue for early_console Chen Gang
2013-03-27 11:55 ` Catalin Marinas [this message]
2013-03-27 12:02 ` Chen Gang
2013-04-03 8:13 ` Chen Gang
2013-04-03 11:39 ` Christopher Covington
2013-04-03 13:00 ` Chen Gang
2013-04-17 9:10 ` Chen Gang
2013-04-19 10:53 ` [PATCH] ARM64: kernel: compiling issue, duplicate definition of early_console Chen Gang
2013-04-19 12:15 ` Arnd Bergmann
2013-04-20 1:55 ` Chen Gang
2013-04-19 12:31 ` Catalin Marinas
2013-04-20 1:54 ` Chen Gang
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=20130327115509.GA1603@MacBook-Pro.local \
--to=catalin.marinas@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=Will.Deacon@arm.com \
--cc=anup.patel@linaro.org \
--cc=arnd@arndb.de \
--cc=gang.chen@asianux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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).