From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Srinivas Kandagatla <srini@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: [PATCH 0/6] ASoC: qcom: Fix confusing cleanup.h
Date: Sat, 29 Nov 2025 14:17:52 +0100 [thread overview]
Message-ID: <20251129-asoc-wrong-cleanup-h-can-people-stop-sending-this-without-reading-docs-v1-0-c38b06884e39@oss.qualcomm.com> (raw)
Please, please stop ending cleanup.h patches for very simple code like:
foo = kzalloc();
kfree(foo);
return;
... *if you do not intend to read cleanup.h*. These changes are making
simple code not necessarily simpler. But worse, if you do not read
cleanup.h then you introduce actually undesired, error-prone and wrong
style of having constructors with redundant values (= NULL).
This is actually worse code.
If you do not agree in declaration-in-place-of-use (fair!), then do not
use cleanup.h. If you want to use cleanup.h, then please read cleanup.h
before.
This is second mixup I see recently around Qualcomm files.
Best regards,
Krzysztof
---
Krzysztof Kozlowski (6):
ASoC: qcom: q6prm: Fix confusing cleanup.h syntax
ASoC: qcom: q6asm: Fix confusing cleanup.h syntax
ASoC: qcom: q6apm: Fix confusing cleanup.h syntax
ASoC: qcom: q6afe: Fix confusing cleanup.h syntax
ASoC: qcom: audioreach: Fix confusing cleanup.h syntax
ASoC: qcom: Minor readability improve with new lines
sound/soc/qcom/qdsp6/audioreach.c | 28 +++++++++++++++++-----------
sound/soc/qcom/qdsp6/q6adm.c | 2 ++
sound/soc/qcom/qdsp6/q6afe.c | 10 ++++++----
sound/soc/qcom/qdsp6/q6apm.c | 9 ++++++---
sound/soc/qcom/qdsp6/q6asm.c | 19 +++++++++++++++----
sound/soc/qcom/qdsp6/q6prm.c | 16 ++++++++--------
6 files changed, 54 insertions(+), 30 deletions(-)
---
base-commit: 92fd6e84175befa1775e5c0ab682938eca27c0b2
change-id: 20251129-asoc-wrong-cleanup-h-can-people-stop-sending-this-without-reading-docs-ebe8abad6e55
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
next reply other threads:[~2025-11-29 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 13:17 Krzysztof Kozlowski [this message]
2025-11-29 13:17 ` [PATCH 1/6] ASoC: qcom: q6prm: Fix confusing cleanup.h syntax Krzysztof Kozlowski
2025-11-29 13:17 ` [PATCH 2/6] ASoC: qcom: q6asm: " Krzysztof Kozlowski
2025-11-29 13:17 ` [PATCH 3/6] ASoC: qcom: q6apm: " Krzysztof Kozlowski
2025-11-29 13:17 ` [PATCH 4/6] ASoC: qcom: q6afe: " Krzysztof Kozlowski
2025-11-29 13:17 ` [PATCH 5/6] ASoC: qcom: audioreach: " Krzysztof Kozlowski
2025-11-29 13:17 ` [PATCH 6/6] ASoC: qcom: Minor readability improve with new lines Krzysztof Kozlowski
2025-12-01 15:12 ` [PATCH 0/6] ASoC: qcom: Fix confusing cleanup.h Srinivas Kandagatla
2025-12-03 8:05 ` Krzysztof Kozlowski
2025-12-15 13:58 ` 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=20251129-asoc-wrong-cleanup-h-can-people-stop-sending-this-without-reading-docs-v1-0-c38b06884e39@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srini@kernel.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).