From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH] ASoC: soc-pcm: tidyup function name to snd_soc_dpcm_be_can_xxx()
Date: Thu, 6 Mar 2025 11:50:30 +0100 [thread overview]
Message-ID: <7b9735d9-8bab-47e4-bee9-77a6c195e562@linux.intel.com> (raw)
In-Reply-To: <87zfhy537a.wl-kuninori.morimoto.gx@renesas.com>
On 3/6/2025 2:59 AM, Kuninori Morimoto wrote:
> We have similar but different function names
>
> snd_soc_dpcm_fe_can_xxx()
> snd_soc_dpcm_be_can_xxx()
> snd_soc_dpcm_can_be_xxx()
> ~~~~~~
> Let's unified these to can_xx
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> sound/soc/soc-pcm.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/sound/soc/soc-pcm.c b/sound/soc/soc-pcm.c
> index 8d88971bdea3..73b05b8f5a07 100644
> --- a/sound/soc/soc-pcm.c
> +++ b/sound/soc/soc-pcm.c
> @@ -36,7 +36,7 @@ static inline int _soc_pcm_ret(struct snd_soc_pcm_runtime *rtd,
>
> /* is the current PCM operation for this FE ? */
> #if 0
> -static int snd_soc_dpcm_fe_can_update(struct snd_soc_pcm_runtime *fe, int stream)
> +static int snd_soc_dpcm_can_fe_update(struct snd_soc_pcm_runtime *fe, int stream)
> {
> if (fe->dpcm[stream].runtime_update == SND_SOC_DPCM_UPDATE_FE)
> return 1;
> @@ -1632,7 +1632,7 @@ void dpcm_be_dai_stop(struct snd_soc_pcm_runtime *fe, int stream,
> return;
>
> /* is this op for this BE ? */
> - if (!snd_soc_dpcm_be_can_update(fe, be, stream))
> + if (!snd_soc_dpcm_can_be_update(fe, be, stream))
Not sure if some part of patch is missing, but shouldn't definition of
snd_soc_dpcm_be_can_update() be converted somewhere? I see only calls
and _fe variant.
next prev parent reply other threads:[~2025-03-06 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 1:59 [PATCH] ASoC: soc-pcm: tidyup function name to snd_soc_dpcm_be_can_xxx() Kuninori Morimoto
2025-03-06 10:50 ` Amadeusz Sławiński [this message]
2025-03-10 1:53 ` Kuninori Morimoto
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=7b9735d9-8bab-47e4-bee9-77a6c195e562@linux.intel.com \
--to=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sound@vger.kernel.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