From: "David S. Miller" <davem@redhat.com>
To: David Dillow <dave@thedillows.org>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Non-PCI build broken on sparc64, maybe others
Date: Mon, 16 Feb 2004 21:32:20 -0800 [thread overview]
Message-ID: <20040216213220.594052c7.davem@redhat.com> (raw)
In-Reply-To: <1076993402.21443.5.camel@ori.thedillows.org>
On 16 Feb 2004 23:50:03 -0500
David Dillow <dave@thedillows.org> wrote:
> I believe this changeset in Linus's tree:
...
> breaks builds that do not include PCI support.
Indeed, thanks for catching this David. This patch should fix it
and I'll be pushing this to Linus.
Thanks again.
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/02/16 21:28:29-08:00 davem@nuts.davemloft.net
# [SPARC64]: Fix non-PCI build, reported by David Dillow.
#
# include/asm-sparc64/dma-mapping.h
# 2004/02/16 21:25:35-08:00 davem@nuts.davemloft.net +21 -1
# [SPARC64]: Fix non-PCI build, reported by David Dillow.
#
diff -Nru a/include/asm-sparc64/dma-mapping.h b/include/asm-sparc64/dma-mapping.h
--- a/include/asm-sparc64/dma-mapping.h Mon Feb 16 21:28:51 2004
+++ b/include/asm-sparc64/dma-mapping.h Mon Feb 16 21:28:51 2004
@@ -1,5 +1,25 @@
+#ifndef _ASM_SPARC64_DMA_MAPPING_H
+#define _ASM_SPARC64_DMA_MAPPING_H
+
#include <linux/config.h>
#ifdef CONFIG_PCI
#include <asm-generic/dma-mapping.h>
-#endif
+#else
+
+static inline void *dma_alloc_coherent(struct device *dev, size_t size,
+ dma_addr_t *dma_handle, int flag)
+{
+ BUG();
+ return NULL;
+}
+
+static inline void dma_free_coherent(struct device *dev, size_t size,
+ void *vaddr, dma_addr_t dma_handle)
+{
+ BUG();
+}
+
+#endif /* PCI */
+
+#endif /* _ASM_SPARC64_DMA_MAPPING_H */
prev parent reply other threads:[~2004-02-17 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 4:50 David Dillow
2004-02-17 5:32 ` David S. Miller [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=20040216213220.594052c7.davem@redhat.com \
--to=davem@redhat.com \
--cc=dave@thedillows.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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
all inboxes | Powered by JetHome®