From: Andrew Morton <akpm@linux-foundation.org>
To: Will Deacon <will.deacon@arm.com>
Cc: Marc.Zyngier@arm.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, ericvh@gmail.com,
levinsasha928@gmail.com
Subject: Re: [PATCH v2 1/3] mm: highmem: export kmap_to_page for modules
Date: Mon, 22 Oct 2012 15:08:18 -0700 [thread overview]
Message-ID: <20121022150818.0e64da3a.akpm@linux-foundation.org> (raw)
In-Reply-To: <1350651813-8694-1-git-send-email-will.deacon@arm.com>
On Fri, 19 Oct 2012 14:03:31 +0100
Will Deacon <will.deacon@arm.com> wrote:
> Some virtio device drivers (9p) need to translate high virtual addresses
> to physical addresses, which are inserted into the virtqueue for
> processing by userspace.
>
> This patch exports the kmap_to_page symbol, so that the affected drivers
> can be compiled as modules.
>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
> ---
> mm/highmem.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/mm/highmem.c b/mm/highmem.c
> index d517cd1..2a07f97 100644
> --- a/mm/highmem.c
> +++ b/mm/highmem.c
> @@ -105,6 +105,7 @@ struct page *kmap_to_page(void *vaddr)
>
> return virt_to_page(addr);
> }
> +EXPORT_SYMBOL(kmap_to_page);
>
Looks OK to me. Would generally prefer that an exported-to-modules
symbol have some documentation, but I guess this one is obvious enough.
Rusty, please include this if you grab the rest of the series.
next prev parent reply other threads:[~2012-10-22 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 13:03 [PATCH v2 1/3] mm: highmem: export kmap_to_page for modules Will Deacon
2012-10-19 13:03 ` [PATCH v2 2/3] virtio: 9p: correctly pass physical address to userspace for high pages Will Deacon
2012-10-22 22:05 ` Andrew Morton
2012-10-19 13:03 ` [PATCH v2 3/3] virtio: force vring descriptors to be allocated from lowmem Will Deacon
2012-10-22 22:08 ` Andrew Morton [this message]
2012-10-22 23:55 ` [PATCH v2 1/3] mm: highmem: export kmap_to_page for modules Rusty Russell
2012-10-23 10:33 ` Will Deacon
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=20121022150818.0e64da3a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Marc.Zyngier@arm.com \
--cc=ericvh@gmail.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=will.deacon@arm.com \
/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).