From: Mark Brown <broonie@kernel.org>
To: "Liam Girdwood" <lgirdwood@gmail.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Nuno Sá" <nuno.sa@analog.com>,
"Srinivas Kandagatla" <srini@kernel.org>,
"Venkata Prasad Potturu" <venkataprasad.potturu@amd.com>,
"Vijendar Mukunda" <Vijendar.Mukunda@amd.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Charles Keepax" <ckeepax@opensource.cirrus.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Peter Zijlstra" <peterz@infradead.org>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
"Qianfeng Rong" <rongqianfeng@vivo.com>
Subject: Re: [PATCH 0/3] ASoC: use int type to store negative error codes
Date: Thu, 28 Aug 2025 23:00:46 +0200 [thread overview]
Message-ID: <175641484651.364214.11154703611395809612.b4-ty@kernel.org> (raw)
In-Reply-To: <20250828075406.386208-1-rongqianfeng@vivo.com>
On Thu, 28 Aug 2025 15:53:56 +0800, Qianfeng Rong wrote:
> The 'ret' variable usually is used to store returns from some functions,
> which return either zero on success or negative error codes on failure.
>
> Storing the negative error codes in unsigned type, doesn't cause an issue
> at runtime but it's ugly as pants. Additionally, assigning negative error
> codes to unsigned type may trigger a GCC warning when the -Wsign-conversion
> flag is enabled.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: amd: use int type to store negative error codes
commit: d985b60f47893e8fd43989662111bebe78311cd1
[2/3] ASoC: adau1977: use int type to store negative error codes
commit: 784771cdd77091e7e93b78b5de55006295cc7b8e
[3/3] ASoC: qcom: use int type to store negative error codes
commit: 11f5c5f9e43e9020bae452232983fe98e7abfce0
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2025-08-28 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 7:53 Qianfeng Rong
2025-08-28 7:53 ` [PATCH 1/3] ASoC: amd: " Qianfeng Rong
2025-08-28 13:30 ` Limonciello, Mario
2025-08-28 7:53 ` [PATCH 2/3] ASoC: adau1977: " Qianfeng Rong
2025-08-28 10:48 ` Nuno Sá
2025-08-28 7:53 ` [PATCH 3/3] ASoC: qcom: " Qianfeng Rong
2025-08-28 10:32 ` Dmitry Baryshkov
2025-08-28 21:00 ` Mark Brown [this message]
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=175641484651.364214.11154703611395809612.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Vijendar.Mukunda@amd.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@kernel.org \
--cc=nuno.sa@analog.com \
--cc=perex@perex.cz \
--cc=peterz@infradead.org \
--cc=rongqianfeng@vivo.com \
--cc=srini@kernel.org \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.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
all inboxes | Powered by JetHome®