All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: <linux-sound@vger.kernel.org>,
	<linux-amlogic@lists.infradead.org>, <s.nawrocki@samsung.com>,
	<lgirdwood@gmail.com>, <broonie@kernel.org>,
	<linux-kernel@vger.kernel.org>, <jbrunet@baylibre.com>
Subject: Re: [RFC v2 1/2] ASoC: soc-dai: add snd_soc_dai_prepare() and use it internally
Date: Mon, 13 Jan 2025 14:13:38 +0000	[thread overview]
Message-ID: <Z4UfkpbDUiJZm2b2@opensource.cirrus.com> (raw)
In-Reply-To: <20250110210730.705613-2-martin.blumenstingl@googlemail.com>

On Fri, Jan 10, 2025 at 10:07:29PM +0100, Martin Blumenstingl wrote:
> Add a new snd_soc_dai_prepare() which can be used (in an upcoming patch)
> by soc-dapm.c. Use this new function internally in
> snd_soc_pcm_dai_prepare() to avoid duplicating code.
> 
> Suggested-by: Jerome Brunet <jbrunet@baylibre.com>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---

Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>

Thanks,
Charles

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

WARNING: multiple messages have this Message-ID (diff)
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: <linux-sound@vger.kernel.org>,
	<linux-amlogic@lists.infradead.org>, <s.nawrocki@samsung.com>,
	<lgirdwood@gmail.com>, <broonie@kernel.org>,
	<linux-kernel@vger.kernel.org>, <jbrunet@baylibre.com>
Subject: Re: [RFC v2 1/2] ASoC: soc-dai: add snd_soc_dai_prepare() and use it internally
Date: Mon, 13 Jan 2025 14:13:38 +0000	[thread overview]
Message-ID: <Z4UfkpbDUiJZm2b2@opensource.cirrus.com> (raw)
In-Reply-To: <20250110210730.705613-2-martin.blumenstingl@googlemail.com>

On Fri, Jan 10, 2025 at 10:07:29PM +0100, Martin Blumenstingl wrote:
> Add a new snd_soc_dai_prepare() which can be used (in an upcoming patch)
> by soc-dapm.c. Use this new function internally in
> snd_soc_pcm_dai_prepare() to avoid duplicating code.
> 
> Suggested-by: Jerome Brunet <jbrunet@baylibre.com>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---

Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>

Thanks,
Charles

  reply	other threads:[~2025-01-13 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 21:07 [RFC v2 0/2] ASoC: prepare streams on codec-to-codec links Martin Blumenstingl
2025-01-10 21:07 ` Martin Blumenstingl
2025-01-10 21:07 ` [RFC v2 1/2] ASoC: soc-dai: add snd_soc_dai_prepare() and use it internally Martin Blumenstingl
2025-01-10 21:07   ` Martin Blumenstingl
2025-01-13 14:13   ` Charles Keepax [this message]
2025-01-13 14:13     ` Charles Keepax
2025-01-10 21:07 ` [RFC v2 2/2] ASoC: dapm: add support for preparing streams Martin Blumenstingl
2025-01-10 21:07   ` Martin Blumenstingl
2025-01-13 14:14   ` Charles Keepax
2025-01-13 14:14     ` Charles Keepax
2025-01-13 14:53 ` [RFC v2 0/2] ASoC: prepare streams on codec-to-codec links Jerome Brunet
2025-01-13 14:53   ` Jerome Brunet

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=Z4UfkpbDUiJZm2b2@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=s.nawrocki@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.