From: Mark Salter <msalter@redhat.com>
To: Chen Baozi <baozich@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
xen-devel@lists.xenproject.org, catalin.marinas@arm.com,
stefano.stabellini@eu.citrix.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/xen: redefine xen_remap on arm64
Date: Mon, 30 Dec 2013 14:20:59 -0500 [thread overview]
Message-ID: <1388431259.2564.15.camel@deneb.redhat.com> (raw)
In-Reply-To: <1388386511-32276-1-git-send-email-baozich@gmail.com>
On Mon, 2013-12-30 at 14:55 +0800, Chen Baozi wrote:
> xen_remap used to be defined as ioremap_cached on arm64. In commit
> c04e8e2fe, a new ioremap_cache was implemented, and ioremap_cached
> was deleted, while xen_remap stays the same. This would lead to
> the failure when building with CONFIG_HVC_XEN. Redefined xen_remap
> on arm64 as ioremap_cache on arm64 to fix it.
>
I missed that include of arm header by arm64 when looking for users
of arm64's ioremap_cached() when working on commit c04e8e2fe. Anyway,
grepping the kernel tree, I see:
ioremap_cached()
defined by: arm, metag, unicore32
used by: arch/arm/include/asm/xen/page.h
drivers/mtd/maps/pxa2xx-flash.c
ioremap_cache()
defined by: arm64, sh, xtensa, ia64, x86
used by: drivers/video/vesafb.c
drivers/char/toshiba.c
drivers/acpi/apei
drivers/lguest/lguest_device.c
drivers/sfi/sfi_core.c
include/linux/acpi_io.h
I think it would be better to just avoid the confusion and the ifdef in
asm/xen/page.h by globally changing ioremap_cached to ioremap_cache.
--Mark
next prev parent reply other threads:[~2013-12-30 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 6:55 Chen Baozi
2013-12-30 9:43 ` [Xen-devel] " Wei Liu
2014-01-03 13:19 ` Stefano Stabellini
2013-12-30 19:20 ` Mark Salter [this message]
2014-01-03 13:13 ` Stefano Stabellini
2014-01-03 13:32 ` Stefano Stabellini
2014-01-03 14:31 ` Russell King - ARM Linux
2014-01-03 14:49 ` Stefano Stabellini
2014-01-03 14:59 ` Russell King - ARM Linux
2014-01-03 15:17 ` Stefano Stabellini
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=1388431259.2564.15.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=baozich@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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®