From: a.othieno@bluewin.ch (Arthur Othieno)
To: akpm@osdl.org
Cc: schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org
Subject: [PATCH] s390: Use include/asm-generic/dma-mapping-broken.h
Date: Sun, 18 Jul 2004 22:29:30 +0200 [thread overview]
Message-ID: <20040718202930.GA9542@mars> (raw)
Hi,
ChangeSet 1.1371.413.23 [1] introduced the file
include/asm-generic/dma-mapping-broken.h for architectures that don't
support the new DMA API. I don't know if this is the case with s390,
however, ChangeSet 1.1371.445.6 [2] introduced a set of changes that
duplicate those in include/asm-generic/dma-mapping-broken.h.
This patch squishes that duplication by simply including
include/asm-generic/dma-mapping-broken.h in
include/asm-s390/dma-mapping.h.
Against 2.6.7, but applies cleanly against 2.6.8-rc2. Thanks.
[1] http://tinyurl.com/7y2d9
[2] http://tinyurl.com/5qybl
Signed-off-by: Arthur Othieno <a.othieno@bluewin.ch>
dma-mapping.h | 13 +------------
1 files changed, 1 insertion(+), 12 deletions(-)
--- a/include/asm-s390/dma-mapping.h 2004-04-11 14:05:20.000000000 +0200
+++ b/include/asm-s390/dma-mapping.h 2004-05-03 00:36:56.000000000 +0200
@@ -9,17 +9,6 @@
#ifndef _ASM_DMA_MAPPING_H
#define _ASM_DMA_MAPPING_H
-static inline void *dma_alloc_coherent(struct device *dev, size_t size,
- dma_addr_t *dma_handle, int flag)
-{
- BUG();
- return 0;
-}
-
-static inline void dma_free_coherent(struct device *dev, size_t size,
- void *vaddr, dma_addr_t dma_handle)
-{
- BUG();
-}
+#include <asm-generic/dma-mapping-broken.h>
#endif /* _ASM_DMA_MAPPING_H */
next reply other threads:[~2004-07-18 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 20:29 Arthur Othieno [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-18 20:23 [PATCH] s390: Use include/asm-generic/dma-mapping-broken.h Arthur Othieno
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=20040718202930.GA9542@mars \
--to=a.othieno@bluewin.ch \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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