From: Arnd Bergmann <arnd@arndb.de>
To: Chen Gang <gang.chen@asianux.com>
Cc: Hirokazu Takata <takata@linux-m32r.org>,
"dhowells@redhat.com" <dhowells@redhat.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-m32r@ml.linux-m32r.org, linux-m32r-ja@ml.linux-m32r.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] arch: m32r: include: asm: add "dma-mapping-common.h"
Date: Thu, 27 Jun 2013 10:30:51 +0200 [thread overview]
Message-ID: <2831217.RWPZkclVnp@wuerfel> (raw)
In-Reply-To: <51CBC4B3.807@asianux.com>
On Thursday 27 June 2013 12:50:59 Chen Gang wrote:
> Need add generic "dma-mapping-common.h", or compiling may fail.
>
> The related error (with allmodconfig):
>
> CC [M] net/irda/irlan/irlan_eth.o
> drivers/media/v4l2-core/videobuf2-dma-contig.c: In function ‘vb2_dc_mmap’:
> drivers/media/v4l2-core/videobuf2-dma-contig.c:202:2: error: implicit declaration of function ‘dma_mmap_coherent’ [-Werror=implicit-function-declaration]
> drivers/media/v4l2-core/videobuf2-dma-contig.c: In function ‘vb2_dc_get_base_sgt’:
> drivers/media/v4l2-core/videobuf2-dma-contig.c:385:2: error: implicit declaration of function ‘dma_get_sgtable’ [-Werror=implicit-function-declaration]
>
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
m32r does not provide the "common" version of the dma mapping API, so this
is certainly wrong.
Arnd
next prev parent reply other threads:[~2013-06-27 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 4:50 [PATCH] arch: m32r: include: asm: add "dma-mapping-common.h" Chen Gang
2013-06-27 8:30 ` Arnd Bergmann [this message]
2013-06-27 9:27 ` Chen Gang
2013-06-27 9:40 ` Chen Gang
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=2831217.RWPZkclVnp@wuerfel \
--to=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=gang.chen@asianux.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m32r-ja@ml.linux-m32r.org \
--cc=linux-m32r@ml.linux-m32r.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=takata@linux-m32r.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.