From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: keystone breakage
Date: Thu, 5 Jun 2014 19:32:23 +0100 [thread overview]
Message-ID: <20140605183223.GF23430@n2100.arm.linux.org.uk> (raw)
It's worth pointing out that with Laura's removal of meminfo, keystone
is now broken - I see that despite Laura's patches being on LAKML for
a while, this fact has been ignored, and now that Keystone support
for the LPAE mappings has been merged, Keystone now breaks:
arch/arm/mach-keystone/keystone.c: In function 'keystone_init_meminfo':
arch/arm/mach-keystone/keystone.c:71:31: error: 'meminfo' undeclared (first use in this function)
I guess this is something that will have to be fixed later.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next reply other threads:[~2014-06-05 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 18:32 Russell King - ARM Linux [this message]
2014-06-05 19:22 ` keystone breakage Santosh Shilimkar
2014-06-05 20:22 ` Arnd Bergmann
2014-06-05 22:46 ` Santosh Shilimkar
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=20140605183223.GF23430@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).