From: ben@decadent.org.uk (Ben Hutchings)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Export dma_set_coherent_mask() implementations
Date: Sat, 27 Nov 2010 22:14:03 +0000 [thread overview]
Message-ID: <1290896043.3292.52.camel@localhost> (raw)
Commit 710224fa2750cf449c02dd115548acebfdd2c86a 'arm: fix "arm: fix
pci_set_consistent_dma_mask for dmabounce devices"' made
dma_set_coherent_mask() an extern function for some ARM platforms.
Since this function is called from many drivers, it must be exported.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Cc: stable at kernel.org [2.6.36]
---
This is not even compile-tested yet, as I don't have a readily available
ARM build system. Should be obvious though, right?
Ben.
arch/arm/common/it8152.c | 1 +
arch/arm/mach-ixp4xx/common-pci.c | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/common/it8152.c b/arch/arm/common/it8152.c
index 60dc077..665708c 100644
--- a/arch/arm/common/it8152.c
+++ b/arch/arm/common/it8152.c
@@ -278,6 +278,7 @@ int dma_set_coherent_mask(struct device *dev, u64 mask)
return -EIO;
}
+EXPORT_SYMBOL(dma_set_coherent_mask);
int __init it8152_pci_setup(int nr, struct pci_sys_data *sys)
{
diff --git a/arch/arm/mach-ixp4xx/common-pci.c b/arch/arm/mach-ixp4xx/common-pci.c
index 24498a9..c3d3d86 100644
--- a/arch/arm/mach-ixp4xx/common-pci.c
+++ b/arch/arm/mach-ixp4xx/common-pci.c
@@ -510,6 +510,7 @@ int dma_set_coherent_mask(struct device *dev, u64 mask)
return -EIO;
}
+EXPORT_SYMBOL(dma_set_coherent_mask);
EXPORT_SYMBOL(ixp4xx_pci_read);
EXPORT_SYMBOL(ixp4xx_pci_write);
--
1.7.2.3
next reply other threads:[~2010-11-27 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 22:14 Ben Hutchings [this message]
2010-11-30 8:14 ` [PATCH] arm: Export dma_set_coherent_mask() implementations Krzysztof Halasa
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=1290896043.3292.52.camel@localhost \
--to=ben@decadent.org.uk \
--cc=linux-arm-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.