From: Markus Elfring <Markus.Elfring@web.de>
To: "Mark Brown" <broonie@kernel.org>,
linux-sound@vger.kernel.org,
sound-open-firmware@alsa-project.org,
"Bard Liao" <yung-chuan.liao@linux.intel.com>,
"Daniel Baluta" <daniel.baluta@nxp.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.dev>,
"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
"Takashi Iwai" <tiwai@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: ASoC: SOF: topology: Use more common error handling code in sof_link_load()
Date: Tue, 30 Jun 2026 19:08:39 +0200 [thread overview]
Message-ID: <2811c5cd-f2a2-418e-a5ba-b1c68ef5f1b9@web.de> (raw)
In-Reply-To: <178281882519.79320.1939247511595511190.b4-ty@b4>
>> ASoC: SOF: topology: Use more common error handling code in sof_link_load()
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.3
>
> Thanks!
>
> [1/1] ASoC: SOF: topology: Use more common error handling code in sof_link_load()
> https://git.kernel.org/broonie/sound/c/a33e6fa400d1
Thanks for another bit of positive feedback.
Will the chances grow that further development ideas also from my change selection
can be integrated better?
Examples:
* ASoC: SOF: topology: Replace devm_kasprintf() call by devm_kstrdup() in sof_copy_tuples()
2025-04-16
https://patchwork.kernel.org/project/alsa-devel/patch/3e473ff5-1554-4065-a305-6b3661e0b941@web.de/
* ASoC: SOF: topology: Move a variable assignment behind condition checks in sof_dai_load()
2023-04-13
https://patchwork.kernel.org/project/alsa-devel/patch/46d8e10e-25dc-dfd7-3e39-92b86058126a@web.de/
Regards,
Markus
next prev parent reply other threads:[~2026-06-30 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 7:56 [PATCH] " Markus Elfring
2026-06-30 11:27 ` Mark Brown
2026-06-30 17:08 ` Markus Elfring [this message]
2026-06-30 18:16 ` Mark Brown
2026-07-01 7:30 ` Markus Elfring
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=2811c5cd-f2a2-418e-a5ba-b1c68ef5f1b9@web.de \
--to=markus.elfring@web.de \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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®