From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: don't call of_dma_request_slave_channel directly
Date: Tue, 23 Apr 2013 16:56:30 +0100 [thread overview]
Message-ID: <20130423155629.GS5019@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1366732475-479886-3-git-send-email-arnd@arndb.de>
On Tue, Apr 23, 2013 at 05:54:33PM +0200, Arnd Bergmann wrote:
> The exported interface for device drivers is dma_request_slave_channel,
> not of_dma_request_slave_channel. The former does not depend on device
> tree but also works with ACPI and other interfaces providing an
> abstraction for DMA channels.
> This fixes link errors when building ALSA as a loadable module.
This has already been changed separately, I'm surprised this applies
against current code. Though one does have to wonder why it's in the
header file if it's not a supported API...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130423/81bf0488/attachment.sig>
next prev parent reply other threads:[~2013-04-23 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 15:54 [PATCH] ARM: allmodconfig regressions in linux-next Arnd Bergmann
2013-04-23 15:54 ` [PATCH] usb: phy: phy core cannot yet be a module Arnd Bergmann
2013-04-23 16:07 ` Felipe Balbi
2013-04-23 16:11 ` Arnd Bergmann
2013-04-23 16:12 ` Felipe Balbi
2013-04-23 16:26 ` Greg Kroah-Hartman
2013-04-23 15:54 ` [PATCH] ASoC: don't call of_dma_request_slave_channel directly Arnd Bergmann
2013-04-23 15:56 ` Mark Brown [this message]
2013-04-24 1:11 ` Shawn Guo
2013-04-24 12:52 ` Arnd Bergmann
2013-04-23 15:54 ` [PATCH] hwrng: bcm2835: fix MODULE_LICENSE tag Arnd Bergmann
2013-06-18 16:57 ` Lubomir Rintel
2013-04-23 15:54 ` [PATCH] clocksource: kona: adapt to CLOCKSOURCE_OF_DECLARE change Arnd Bergmann
2013-04-26 15:42 ` Christian Daudt
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=20130423155629.GS5019@opensource.wolfsonmicro.com \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).