From: Andreas Schwab <schwab@suse.de>
To: Gary Guo <gary@garyguo.net>
Cc: "linux-riscv@lists.infradead.org" <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] riscv: move flush_icache_{all, mm} code to proper location
Date: Tue, 21 May 2019 12:38:55 +0200 [thread overview]
Message-ID: <mvmk1ekhz28.fsf@suse.de> (raw)
In-Reply-To: <LO2P265MB0847855A503C55BB11A59A89D6730@LO2P265MB0847.GBRP265.PROD.OUTLOOK.COM> (Gary Guo's message of "Wed, 6 Mar 2019 17:00:21 +0000")
On Mär 06 2019, Gary Guo <gary@garyguo.net> wrote:
> diff --git a/arch/riscv/include/asm/cacheflush.h b/arch/riscv/include/asm/cacheflush.h
> index 8f13074413a7..1f4ba68ab9aa 100644
> --- a/arch/riscv/include/asm/cacheflush.h
> +++ b/arch/riscv/include/asm/cacheflush.h
> @@ -47,7 +47,7 @@ static inline void flush_dcache_page(struct page *page)
>
> #else /* CONFIG_SMP */
>
> -#define flush_icache_all() sbi_remote_fence_i(NULL)
> +void flush_icache_all(void);
> void flush_icache_mm(struct mm_struct *mm, bool local);
ERROR: "flush_icache_all" [drivers/misc/lkdtm/lkdtm.ko] undefined!
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2019-05-21 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 17:00 [PATCH] riscv: move flush_icache_{all,mm} code to proper location Gary Guo
2019-03-08 14:24 ` [PATCH] riscv: move flush_icache_{all, mm} " Christoph Hellwig
2019-03-08 15:23 ` Gary Guo
2019-03-08 16:28 ` Christoph Hellwig
2019-05-21 10:38 ` Andreas Schwab [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=mvmk1ekhz28.fsf@suse.de \
--to=schwab@suse.de \
--cc=gary@garyguo.net \
--cc=linux-riscv@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).