From: Dan Murphy <dmurphy@ti.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Simon Horman <horms@verge.net.au>, Chris Ball <cjb@laptop.org>,
linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@linaro.org>
Subject: Re: [PATCH v2] dmaengine: shdma: fix a build failure on platforms with no DMA support
Date: Fri, 31 May 2013 06:18:31 -0500 [thread overview]
Message-ID: <51A88707.4040601@ti.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1305310423360.1470@axis700.grange>
On 05/30/2013 10:01 PM, Guennadi Liakhovetski wrote:
> On platforms with no support for the shdma dmaengine driver build is
> currently failing with
>
> drivers/built-in.o: In function `sh_mobile_sdhi_probe':
> drivers/mmc/host/sh_mobile_sdhi.c:170: undefined reference to`shdma_chan_filter'
>
> Fix the breakage by defining shdma_chan_filter to NULL in such
> configurations.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
> ---
>
> v2: in "next" shdma_chan_filter() is defined in shdma-base.c, which is
> built if CONFIG_SH_DMAE_BASE is defined. This version uses the correct
> symbol.
>
> This is for "next." Compile-tested only. I'll test it on hardware next
> week, but I don't think it shall break anything.
>
> include/linux/sh_dma.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/sh_dma.h b/include/linux/sh_dma.h
> index b64d6be..1fd8a20 100644
> --- a/include/linux/sh_dma.h
> +++ b/include/linux/sh_dma.h
> @@ -99,6 +99,10 @@ struct sh_dmae_pdata {
> #define CHCR_TE 0x00000002
> #define CHCR_IE 0x00000004
>
> +#if IS_ENABLED(CONFIG_SH_DMAE_BASE)
> bool shdma_chan_filter(struct dma_chan *chan, void *arg);
> +#else
> +#define shdma_chan_filter NULL
OK I did not see a reply to my previous comment
Would this not be better as a
#else
static inline bool shdma_chan_filter(struct dma_chan *chan, void *arg) { return false; }
#endif
Otherwise runtime will call a NULL pointer
> +#endif
>
> #endif
--
------------------
Dan Murphy
next prev parent reply other threads:[~2013-05-31 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 3:01 [PATCH v2] dmaengine: shdma: fix a build failure on platforms with no DMA support Guennadi Liakhovetski
2013-05-31 11:18 ` Dan Murphy [this message]
2013-05-31 13:08 ` Guennadi Liakhovetski
2013-05-31 15:00 ` Dan Murphy
2013-05-31 15:04 ` Arnd Bergmann
2013-05-31 14:51 ` Arnd Bergmann
2013-06-27 13:49 ` Simon Horman
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=51A88707.4040601@ti.com \
--to=dmurphy@ti.com \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@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