From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: shumingf@realtek.com
Cc: broonie@kernel.org, lgirdwood@gmail.com,
linux-sound@vger.kernel.org, lars@metafoo.de, flove@realtek.com,
oder_chiou@realtek.com, jack.yu@realtek.com,
derek.fang@realtek.com
Subject: Re: [PATCH 2/2] ASoC: SDCA: fix finding wrong entity
Date: Wed, 25 Mar 2026 10:16:27 +0000 [thread overview]
Message-ID: <acO1+yld0mhWjxvW@opensource.cirrus.com> (raw)
In-Reply-To: <20260325092028.3221671-1-shumingf@realtek.com>
On Wed, Mar 25, 2026 at 05:20:28PM +0800, shumingf@realtek.com wrote:
> From: Shuming Fan <shumingf@realtek.com>
>
> This patch fixes an issue like:
> where searching for the entity 'FU 11' could incorrectly match 'FU 113' first.
> The driver should first perform an exact match on the full string name.
> If no exact match is found, it can then fall back to a partial match.
>
> Signed-off-by: Shuming Fan <shumingf@realtek.com>
Could use a fixes tag:
Fixes: 48fa77af2f4a ("ASoC: SDCA: Add terminal type into input/output widget name")
> ---
> sound/soc/sdca/sdca_functions.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/sound/soc/sdca/sdca_functions.c b/sound/soc/sdca/sdca_functions.c
> index 0b7d97dcb236..0787bf024d21 100644
> --- a/sound/soc/sdca/sdca_functions.c
> +++ b/sound/soc/sdca/sdca_functions.c
> @@ -1602,9 +1602,18 @@ static struct sdca_entity *find_sdca_entity_by_label(struct sdca_function_data *
> const char *entity_label)
> {
> int i;
> + struct sdca_entity *entity = NULL;
Minor nit put this above the int i;
But looks like a good fix, thanks for spotting that.
Thanks,
Charles
next prev parent reply other threads:[~2026-03-25 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 9:20 [PATCH 2/2] ASoC: SDCA: fix finding wrong entity shumingf
2026-03-25 10:16 ` Charles Keepax [this message]
2026-03-25 10:51 ` Shuming [范書銘]
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=acO1+yld0mhWjxvW@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=shumingf@realtek.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