From: Krzysztof Kozlowski <krzk@kernel.org>
To: shao.mingyin@zte.com.cn, olivier.moysan@foss.st.com
Cc: arnaud.pouliquen@foss.st.com, lgirdwood@gmail.com,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
linux-sound@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, yang.yang29@zte.com.cn,
xu.xin16@zte.com.cn, ye.xingchen@zte.com.cn,
zhang.enpei@zte.com.cn
Subject: Re: [PATCH] sound: soc: stm: stm32_sai: Use dev_err_probe()
Date: Fri, 4 Apr 2025 08:12:59 +0200 [thread overview]
Message-ID: <8ae5b493-6906-4adc-8983-d343c7803f06@kernel.org> (raw)
In-Reply-To: <20250403154142936Po-soX8Bifyvw_eWSbddT@zte.com.cn>
On 03/04/2025 09:41, shao.mingyin@zte.com.cn wrote:
> From: Zhang Enpei <zhang.enpei@zte.com.cn>
>
> Replace the open-code with dev_err_probe() to simplify the code.
>
> Signed-off-by: Zhang Enpei <zhang.enpei@zte.com.cn>
> Signed-off-by: Shao Mingyin <shao.mingyin@zte.com.cn>
> ---
The code was correct before 2cfe1ff22555 ("ASoC: stm32: sai: add
stm32mp25 support") and that commit broke it. Some explanation would be
useful instead of blindly generating patches.
Was it done on purpose like that in that commit? Or ST just sent
downstream commit to mainline without changing it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-04 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 7:41 [PATCH] sound: soc: stm: stm32_sai: Use dev_err_probe() shao.mingyin
2025-04-03 11:10 ` Mark Brown
2025-04-04 6:12 ` Krzysztof Kozlowski [this message]
2025-04-07 23:35 ` 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=8ae5b493-6906-4adc-8983-d343c7803f06@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=arnaud.pouliquen@foss.st.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@foss.st.com \
--cc=perex@perex.cz \
--cc=shao.mingyin@zte.com.cn \
--cc=tiwai@suse.com \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=ye.xingchen@zte.com.cn \
--cc=zhang.enpei@zte.com.cn \
/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