From: Wolfgang Grandegger <wg@grandegger.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christian Pellegrin <chripell@fsfe.org>,
"David S. Miller" <davem@davemloft.net>,
Urs Thuermann <urs.thuermann@volkswagen.de>,
Oliver Hartkopp <oliver.hartkopp@volkswagen.de>,
netdev@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] can: CAN_MCP251X should depend on HAS_DMA
Date: Sun, 13 Dec 2009 21:47:04 +0100 [thread overview]
Message-ID: <4B2552C8.4090105@grandegger.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0912132008100.21225@ayla.of.borg>
Geert Uytterhoeven wrote:
> When building for Sun 3:
>
> drivers/net/can/mcp251x.c:1074: undefined reference to `dma_free_coherent'
> drivers/net/can/mcp251x.c:976: undefined reference to `dma_alloc_coherent'
> drivers/net/can/mcp251x.c:1050: undefined reference to `dma_free_coherent'
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> drivers/net/can/Kconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig
> index 8c485aa..05b7517 100644
> --- a/drivers/net/can/Kconfig
> +++ b/drivers/net/can/Kconfig
> @@ -50,7 +50,7 @@ config CAN_TI_HECC
>
> config CAN_MCP251X
> tristate "Microchip MCP251x SPI CAN controllers"
> - depends on CAN_DEV && SPI
> + depends on CAN_DEV && SPI && HAS_DMA
> ---help---
> Driver for the Microchip MCP251x SPI CAN controllers.
>
DMA can be selected with the module parameter "mcp251x_enable_dma" and
is *off* by default. Therefore the driver does in principle not depend
on HAS_DMA but I'm not sure if it's worth to handle it with #idef's.
Christian? Any thought?
Wolfgang.
next prev parent reply other threads:[~2009-12-13 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 19:11 [PATCH] can: CAN_MCP251X should depend on HAS_DMA Geert Uytterhoeven
2009-12-13 20:47 ` Wolfgang Grandegger [this message]
2009-12-14 1:40 ` David Miller
2009-12-14 7:34 ` Wolfgang Grandegger
2009-12-14 8:14 ` christian pellegrin
2009-12-14 3:58 ` David Miller
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=4B2552C8.4090105@grandegger.com \
--to=wg@grandegger.com \
--cc=chripell@fsfe.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
--cc=urs.thuermann@volkswagen.de \
/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;
as well as URLs for NNTP newsgroup(s).