From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: kuninori.morimoto.gx@renesas.com
Cc: linux-sh@vger.kernel.org,
Linux-ALSA <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Magnus Damm <magnus.damm@gmail.com>,
Paul Mundt <lethal@linux-sh.org>, Liam Girdwood <lrg@ti.com>
Subject: Re: [alsa-devel] ASoC: sh: fsi: Build proble in 3.4-rc4
Date: Mon, 23 Apr 2012 20:02:58 +0000 [thread overview]
Message-ID: <201204232202.58584.rjw@sisk.pl> (raw)
In-Reply-To: <87fwbv9v47.wl%kuninori.morimoto.gx@renesas.com>
On Monday, April 23, 2012, kuninori.morimoto.gx@renesas.com wrote:
>
> Hi Rafael
>
> > There is a build problem in sound/soc/sh/fsi.c which seems to be fixed by
> > the following patch. I'm unsure if that is the right fix, though.
>
> Thank you about this patch.
> But this issue was solved by below patch on Mark's/for-3.4 branch
OK, thanks.
Rafael
> ------------------------------------------------
> commit cdf27f373781d8740b874b0b5c18142df32ebb52
> Author: Paul Mundt <lethal@linux-sh.org>
> Date: Tue Apr 17 19:13:04 2012 -0700
>
> ASoC: fsi: update for dmaengine prep_slave_sg fallout.
>
> Leading up to the ->device_prep_slave_sg change in
> 185ecb5f4fd43911c35956d4cc7d94a1da30417f 'dmaengine: add context
> parameter to prep_slave_sg and prep_dma_cyclic' a generic wrapper was
> added in place to guard against the API change, though the fsi driver
> wasn't updated in the process (presumably its dmaengine support hadn't
> been merged yet at the time). This trivially switches over to the new
> wrapper and gets it building again.
>
> Signed-off-by: Paul Mundt <lethal@linux-sh.org>
> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ------------------------------------------------
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2012-04-23 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 21:59 ASoC: sh: fsi: Build proble in 3.4-rc4 Rafael J. Wysocki
2012-04-22 23:58 ` [alsa-devel] " kuninori.morimoto.gx
2012-04-23 20:02 ` Rafael J. Wysocki [this message]
2012-04-24 10:57 ` Mark Brown
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=201204232202.58584.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
--cc=lrg@ti.com \
--cc=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).