From: Felipe Balbi <me@felipebalbi.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: OMAP: Fix Gumstix Overo machine driver by using snd_soc_dai struct
Date: Fri, 12 Sep 2008 23:46:18 +0300 [thread overview]
Message-ID: <20080912204618.GJ7132@frodo> (raw)
In-Reply-To: <5e088bd90809121342i1f7f360fk6ae6123cc54556b6@mail.gmail.com>
On Fri, Sep 12, 2008 at 01:42:42PM -0700, Steve Sakoman wrote:
should this be From: Jarkko ???
> Structs snd_soc_codec_dai and snd_soc_cpu_dai are obsolete and are merged to
> snd_soc_dai by the commit 8687eb8bded8c3c5842a85bd0c30e43fc5a3e0e0.
>
> Signed-off-by: Jarkko Nikula <jarkko.nikula@nokia.com>
> Acked-by: Steve Sakoman <steve@sakoman.com>
> ---
> sound/soc/omap/overo.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/omap/overo.c b/sound/soc/omap/overo.c
> index 542ff6b..1a086ce 100644
> --- a/sound/soc/omap/overo.c
> +++ b/sound/soc/omap/overo.c
> @@ -39,8 +39,8 @@ static int overo_hw_params(struct snd_pcm_substream
> *substream,
> struct snd_pcm_hw_params *params)
> {
> struct snd_soc_pcm_runtime *rtd = substream->private_data;
> - struct snd_soc_codec_dai *codec_dai = rtd->dai->codec_dai;
> - struct snd_soc_cpu_dai *cpu_dai = rtd->dai->cpu_dai;
> + struct snd_soc_dai *codec_dai = rtd->dai->codec_dai;
> + struct snd_soc_dai *cpu_dai = rtd->dai->cpu_dai;
> int ret;
>
> /* Set codec DAI configuration */
--
balbi
next prev parent reply other threads:[~2008-09-12 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 20:42 [PATCH] ASoC: OMAP: Fix Gumstix Overo machine driver by using snd_soc_dai struct Steve Sakoman
2008-09-12 20:46 ` Felipe Balbi [this message]
2008-09-12 20:50 ` Steve Sakoman
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=20080912204618.GJ7132@frodo \
--to=me@felipebalbi.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@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