Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	Jyri Sarha <jsarha@ti.com>, Mark Brown <broonie@kernel.org>,
	notasas@gmail.com, Jarkko Nikula <jarkko.nikula@bitmer.com>
Subject: Re: [PATCH v2 09/20] ASoC: omap-hdmi: Bind the platform driver to the dai driver when loading
Date: Mon, 21 Apr 2014 14:54:41 +0200	[thread overview]
Message-ID: <53551511.50104@metafoo.de> (raw)
In-Reply-To: <1397652390-852-10-git-send-email-peter.ujfalusi@ti.com>

On 04/16/2014 02:46 PM, Peter Ujfalusi wrote:
[...]
> +	return omap_pcm_platform_register(&pdev->dev);
> +}
>   }
There is a excess } here.

  reply	other threads:[~2014-04-21 12:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 12:46 [PATCH v2 00/20] ASoC: omap: Bind the omap-pcm platform driver to dai device Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 01/20] ASoC: Add resource managed snd_soc_register_platform() Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 02/20] ASoC: omap-pcm: Support for binding the platform driver to dai devices Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 03/20] ASoC: omap-mcpdm: Assign the dai DMA data at earlier time Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 04/20] ASoC: omap-mcpdm: Bind the platform driver to the dai driver when loading Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 05/20] ASoC: omap-mcbsp: Assign the dai DMA data at earlier time Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 06/20] ASoC: omap-mcbsp: Bind the platform driver to the dai driver when loading Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 07/20] ASoC: omap-dmic: Assign the dai DMA data at earlier time Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 08/20] ASoC: omap-dmic: Bind the platform driver to the dai driver when loading Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 09/20] ASoC: omap-hdmi: " Peter Ujfalusi
2014-04-21 12:54   ` Lars-Peter Clausen [this message]
2014-04-22  7:26     ` Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 10/20] ASoC: davinci-mcasp: Update MCASP_VERSION_4 platform driver registration Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 11/20] ASoC: omap-abe-twl6040: Use the cpu_dai node to specify the platform driver Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 12/20] ASoC: omap-twl4030: Use the same name/node for platform as the cpu_dai Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 13/20] ASoC: am3517evm: Use the same name " Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 14/20] ASoC: ams-delta: " Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 15/20] ASoC: n810: " Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 16/20] ASoC: omap3pandora: " Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 17/20] ASoC: osk5912: " Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 18/20] ASoC: rx51: " Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 19/20] ASoC: omap-hdmi-card: " Peter Ujfalusi
2014-04-16 12:46 ` [PATCH v2 20/20] ASoC: omap-pcm: Drop the platform driver init code Peter Ujfalusi
2014-04-18 17:05 ` [PATCH v2 00/20] ASoC: omap: Bind the omap-pcm platform driver to dai device 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=53551511.50104@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jarkko.nikula@bitmer.com \
    --cc=jsarha@ti.com \
    --cc=lgirdwood@gmail.com \
    --cc=notasas@gmail.com \
    --cc=peter.ujfalusi@ti.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