From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org,
Loic Pallardy <loic.pallardy@st.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/4] dma-mapping: remove the dma_declare_coherent_memory export
Date: Mon, 2 Sep 2019 22:07:46 +0200 [thread overview]
Message-ID: <20190902200746.16185-5-hch@lst.de> (raw)
In-Reply-To: <20190902200746.16185-1-hch@lst.de>
dma_declare_coherent_memory is something that the platform setup code
(which pretty much means the device tree these days) need to do so that
drivers can use the memory as declared by the platform. Drivers
themselves have no business calling this function.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
kernel/dma/coherent.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/dma/coherent.c b/kernel/dma/coherent.c
index 7cafe1affdc9..545e3869b0e3 100644
--- a/kernel/dma/coherent.c
+++ b/kernel/dma/coherent.c
@@ -122,7 +122,6 @@ int dma_declare_coherent_memory(struct device *dev, phys_addr_t phys_addr,
dma_release_coherent_memory(mem);
return ret;
}
-EXPORT_SYMBOL(dma_declare_coherent_memory);
static void *__dma_alloc_from_coherent(struct dma_coherent_mem *mem,
ssize_t size, dma_addr_t *dma_handle)
--
2.20.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2019-09-02 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 20:07 remove various dma_declare_coherent related exports Christoph Hellwig
2019-09-02 20:07 ` [PATCH 1/4] dma-mapping: remove dma_release_declared_memory Christoph Hellwig
2019-09-02 20:07 ` [PATCH 2/4] dma-mapping: remove the dma_mmap_from_dev_coherent export Christoph Hellwig
2019-09-02 20:07 ` [PATCH 3/4] remoteproc: don't allow modular build Christoph Hellwig
2019-09-03 21:07 ` Bjorn Andersson
2019-09-04 9:05 ` Christoph Hellwig
2019-09-02 20:07 ` Christoph Hellwig [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=20190902200746.16185-5-hch@lst.de \
--to=hch@lst.de \
--cc=bjorn.andersson@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=ohad@wizery.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).