From: Robin Murphy <robin.murphy@arm.com>
To: Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: fix pmem interface definition
Date: Thu, 10 Aug 2017 17:33:17 +0100 [thread overview]
Message-ID: <de4edef8-cf9e-8d0f-b399-9a5796c29680@arm.com> (raw)
In-Reply-To: <20170810145253.2124019-1-arnd@arndb.de>
On 10/08/17 15:52, Arnd Bergmann wrote:
> Defining the two functions as 'static inline' and exporting them
> leads to the interesting case where we can use the interface
> from loadable modules, but not from built-in drivers, as shown
> in this link failure:
>
> vers/nvdimm/claim.o: In function `nsio_rw_bytes':
> claim.c:(.text+0x1b8): undefined reference to `arch_invalidate_pmem'
> drivers/nvdimm/pmem.o: In function `pmem_dax_flush':
> pmem.c:(.text+0x11c): undefined reference to `arch_wb_cache_pmem'
> drivers/nvdimm/pmem.o: In function `pmem_make_request':
> pmem.c:(.text+0x5a4): undefined reference to `arch_invalidate_pmem'
> pmem.c:(.text+0x650): undefined reference to `arch_invalidate_pmem'
> pmem.c:(.text+0x6d4): undefined reference to `arch_invalidate_pmem'
>
> This removes the bogus 'static inline'.
Oops, yes, this was clearly a silly copy-paste error on my part.
Acked-by: Robin Murphy <robin.murphy@arm.com>
> Fixes: d50e071fdaa3 ("arm64: Implement pmem API support")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> arch/arm64/mm/flush.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/mm/flush.c b/arch/arm64/mm/flush.c
> index 280f90ff33a2..e36ed5087b5c 100644
> --- a/arch/arm64/mm/flush.c
> +++ b/arch/arm64/mm/flush.c
> @@ -85,7 +85,7 @@ EXPORT_SYMBOL(flush_dcache_page);
> EXPORT_SYMBOL(flush_icache_range);
>
> #ifdef CONFIG_ARCH_HAS_PMEM_API
> -static inline void arch_wb_cache_pmem(void *addr, size_t size)
> +void arch_wb_cache_pmem(void *addr, size_t size)
> {
> /* Ensure order against any prior non-cacheable writes */
> dmb(osh);
> @@ -93,7 +93,7 @@ static inline void arch_wb_cache_pmem(void *addr, size_t size)
> }
> EXPORT_SYMBOL_GPL(arch_wb_cache_pmem);
>
> -static inline void arch_invalidate_pmem(void *addr, size_t size)
> +void arch_invalidate_pmem(void *addr, size_t size)
> {
> __inval_dcache_area(addr, size);
> }
>
next prev parent reply other threads:[~2017-08-10 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 14:52 Arnd Bergmann
2017-08-10 16:33 ` Robin Murphy [this message]
2017-08-10 17:14 ` Catalin Marinas
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=de4edef8-cf9e-8d0f-b399-9a5796c29680@arm.com \
--to=robin.murphy@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®