From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: compat: fix compilation when using 64kB pages
Date: Mon, 15 Jul 2013 11:02:43 +0100 [thread overview]
Message-ID: <20130715100243.GA10000@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1373553036-5418-1-git-send-email-marc.zyngier@arm.com>
On Thu, Jul 11, 2013 at 03:30:36PM +0100, Marc Zyngier wrote:
> When compiling for 64kB pages, we end-up having conflicting
> implementations for aarch32_break_handler().
>
> Wrap the 4kB page implementation with a CONFIG_COMPAT guard and change
> the !CONFIG_COMPAT implementation to be static inline instead of simply static.
>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
I think there was a better fix kicking around for this from Chen Gang already.
I asked for a new commit message, but a v3 didn't appear:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/179418.html
Will
prev parent reply other threads:[~2013-07-15 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 14:30 [PATCH] arm64: compat: fix compilation when using 64kB pages Marc Zyngier
2013-07-15 10:02 ` Will Deacon [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=20130715100243.GA10000@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--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).