From: julien.grall@linaro.org (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/xen: Remove definiition of virt_to_pfn in asm/xen/page.h
Date: Thu, 24 Apr 2014 13:49:09 +0100 [thread overview]
Message-ID: <53590845.1090405@linaro.org> (raw)
In-Reply-To: <535901F0.3010908@citrix.com>
Hi David,
On 04/24/2014 01:22 PM, David Vrabel wrote:
> On 18/04/14 16:54, Julien Grall wrote:
>> virt_to_pfn has been defined in asm/memory.h by the commit e26a9e0 "ARM: Better
>> virt_to_page() handling"
>>
>> This will result of a compilation warning when CONFIG_XEN is enabled.
>>
>> arch/arm/include/asm/xen/page.h:80:0: warning: "virt_to_pfn" redefined [enabled by default]
>> #define virt_to_pfn(v) (PFN_DOWN(__pa(v)))
>> ^
>> In file included from arch/arm/include/asm/page.h:163:0,
>> from arch/arm/include/asm/xen/page.h:4,
>> from include/xen/page.h:4,
>> from arch/arm/xen/grant-table.c:33:
>>
>> The definition in memory.h is nearly the same (it directly expand PFN_DOWN),
>> so we can safely drop virt_to_pfn in xen include.
>
>
> This breaks the arm build for me.
>
> /local/davidvr/work/k.org/tip/drivers/block/xen-blkfront.c: In function
> ?setup_blkring?:
> /local/davidvr/work/k.org/tip/drivers/block/xen-blkfront.c:1236:2:
> error: implicit declaration of function ?virt_to_pfn?
> [-Werror=implicit-function-declaration]
> err = xenbus_grant_ring(dev, virt_to_mfn(info->ring.sring));
> ^
I don't have any issue to build the following branch with this patch on:
- v3.15-rc2
- xentip master
- xentip for-linus-3.16
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-04-24 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 15:54 [PATCH] arm/xen: Remove definiition of virt_to_pfn in asm/xen/page.h Julien Grall
2014-04-24 12:22 ` David Vrabel
2014-04-24 12:49 ` Julien Grall [this message]
2014-04-24 14:11 ` David Vrabel
2014-04-25 17:05 ` Stefano Stabellini
2014-05-07 11:41 ` Stefano Stabellini
2014-05-07 11:46 ` David Vrabel
2014-05-07 16:58 ` Stefano Stabellini
2014-05-08 11:05 ` Catalin Marinas
2014-05-08 15:54 ` 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=53590845.1090405@linaro.org \
--to=julien.grall@linaro.org \
--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).