linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang Wenhu <wenhu.wang@hotmail.com>
To: gregkh@linuxfoundation.org, christophe.leroy@csgroup.eu
Cc: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, Wang Wenhu <wenhu.wang@hotmail.com>
Subject: [PATCH 1/2] powerpc:mm: export symbol ioremap_coherent
Date: Thu,  9 Jun 2022 03:28:54 -0700	[thread overview]
Message-ID: <SG2PR01MB2951EBFD4C4EB2A2519FF4199FA79@SG2PR01MB2951.apcprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <20220609102855.272270-1-wenhu.wang@hotmail.com>

The function ioremap_coherent may be called by modules such as
fsl_85xx_cache_sram. So export it for access in other modules.

Signed-off-by: Wang Wenhu <wenhu.wang@hotmail.com>
---
 arch/powerpc/mm/ioremap.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/powerpc/mm/ioremap.c b/arch/powerpc/mm/ioremap.c
index 4f12504fb405..08a00dacef0b 100644
--- a/arch/powerpc/mm/ioremap.c
+++ b/arch/powerpc/mm/ioremap.c
@@ -40,6 +40,7 @@ void __iomem *ioremap_coherent(phys_addr_t addr, unsigned long size)
 		return iowa_ioremap(addr, size, prot, caller);
 	return __ioremap_caller(addr, size, prot, caller);
 }
+EXPORT_SYMBOL(ioremap_coherent);
 
 void __iomem *ioremap_prot(phys_addr_t addr, unsigned long size, unsigned long flags)
 {
-- 
2.25.1


       reply	other threads:[~2022-06-09 10:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220609102855.272270-1-wenhu.wang@hotmail.com>
2022-06-09 10:28 ` Wang Wenhu [this message]
2022-06-14 10:45   ` [PATCH 1/2] powerpc:mm: export symbol ioremap_coherent Michael Ellerman
2022-06-14 14:49     ` Christoph Hellwig
2022-06-15  4:37     ` 回复: " Wenhu Wang
2022-06-09 10:28 ` [PATCH 2/2] uio:powerpc:mpc85xx: l2-cache-sram uio driver implementation Wang Wenhu
2022-06-09 13:17   ` Greg KH
2022-06-14  6:09     ` 回复: " Wenhu Wang
2022-06-14  6:34       ` Greg KH
2022-06-14  7:12         ` Christophe Leroy
2022-06-14  7:18       ` Christophe Leroy
2022-06-14  7:26         ` Christophe Leroy
2022-06-14  7:53           ` Wenhu Wang
2022-06-14  8:03             ` Greg KH
2022-06-14  8:39               ` Wenhu Wang
2022-06-14 14:40             ` Wenhu Wang
2022-06-14 14:59               ` Christophe Leroy
2022-06-15  6:04       ` 回复: " Christophe Leroy
2022-06-15  5:57     ` [PATCHv2 0/2] uio:powerpc:mpc85xx: l2-cache-sram uio driver Wang Wenhu
     [not found]     ` <20220615055735.53585-1-wenhu.wang@hotmail.com>
2022-06-15  5:57       ` [PATCHv2 1/2] mm: eliminate ifdef of HAVE_IOREMAP_PROT in .c files Wang Wenhu
2022-06-15  6:49         ` Christoph Hellwig
2022-06-22  2:22         ` kernel test robot
2022-06-22  4:13         ` kernel test robot
2022-06-15  5:57       ` [PATCHv2 2/2] uio:powerpc:mpc85xx: l2-cache-sram uio driver implementation Wang Wenhu
2022-06-15  6:43         ` Christoph Hellwig
2022-06-15  6:48         ` Christophe Leroy
2022-06-15  6:49         ` Christophe Leroy
2022-06-14 14:51   ` [PATCH " Christoph Hellwig

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=SG2PR01MB2951EBFD4C4EB2A2519FF4199FA79@SG2PR01MB2951.apcprd01.prod.exchangelabs.com \
    --to=wenhu.wang@hotmail.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).