From: Arnd Bergmann <arnd@arndb.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Kevin Cernekee <cernekee@gmail.com>,
grant.likely@linaro.org, kbuild-all@01.org,
gregkh@linuxfoundation.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Hirokazu Takata <takata@linux-m32r.org>
Subject: Re: [PATCH V2 2/2] m32r: Add missing big-endian I/O accessors
Date: Fri, 28 Nov 2014 00:15:08 +0100 [thread overview]
Message-ID: <3737870.23qKxazWvK@wuerfel> (raw)
In-Reply-To: <20141127222034.GB16647@wfg-t540p.sh.intel.com>
On Thursday 27 November 2014 14:20:34 Fengguang Wu wrote:
> Add CC to Hirokazu.
>
> > Side note for Fengguang: both with and without my patches, m32r modules
> > fail to link using the make.cross script on Ubuntu 14.10:
>
> Yes, the memory_start/memory_end link errors are really old m32r
> specific errors. The config file that can trigger this error is
> m32r-m32104ut_defconfig.
These should be trivial to fix:
diff --git a/arch/m32r/kernel/setup.c b/arch/m32r/kernel/setup.c
index 0392112a5d70..a5ecef7188ba 100644
--- a/arch/m32r/kernel/setup.c
+++ b/arch/m32r/kernel/setup.c
@@ -81,7 +81,10 @@ static struct resource code_resource = {
};
unsigned long memory_start;
+EXPORT_SYMBOL(memory_start);
+
unsigned long memory_end;
+EXPORT_SYMBOL(memory_end);
void __init setup_arch(char **);
int get_cpuinfo(char *);
Arnd
prev parent reply other threads:[~2014-11-27 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 18:16 [PATCH V2 1/2] m32r: Fix ioread8 definition Kevin Cernekee
2014-11-27 18:16 ` [PATCH V2 2/2] m32r: Add missing big-endian I/O accessors Kevin Cernekee
2014-11-27 21:48 ` Arnd Bergmann
2014-11-27 22:20 ` Fengguang Wu
2014-11-27 23:15 ` Arnd Bergmann [this message]
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=3737870.23qKxazWvK@wuerfel \
--to=arnd@arndb.de \
--cc=cernekee@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fengguang.wu@intel.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=takata@linux-m32r.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
all inboxes | Powered by JetHome®