From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: linux-sound@vger.kernel.org, kai.vehmanen@linux.intel.com,
ranjani.sridharan@linux.intel.com,
yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev
Subject: Re: [PATCH 0/4] ASoC: SOF: Improve the spcm and ipc4 copier prints
Date: Fri, 07 Feb 2025 14:02:43 +0000 [thread overview]
Message-ID: <173893696397.35212.580149591364875425.b4-ty@kernel.org> (raw)
In-Reply-To: <20250206092828.7569-1-peter.ujfalusi@linux.intel.com>
On Thu, 06 Feb 2025 11:28:24 +0200, Peter Ujfalusi wrote:
> Introduce new wrapper to present spcm related debug and error prints in
> a unified way and provide additional details to help to understand the
> reasons and configuration used when the log was captured.
>
> Change the way we print information about the ipc4 copier module to
> use type specific prints, again to provide better information for
> debugging.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: SOF: Relocate and rework functionality for PCM stream freeing
commit: 169ec0a541aac8afb215ab591b0fd53276686014
[2/4] ASoC: SOF: pcm: Move period/buffer configuration print after platform open
commit: 4d2ea16576c8aa1437048cf436bff85653f139fe
[3/4] ASoC: SOF: pcm: Add snd_sof_pcm specific wrappers for dev_dbg() and dev_err()
commit: 860693187c597645b28a421d8acb26428b8afd3f
[4/4] ASoC: SOF: ipc4-topology: Improve the information in prepare_copier prints
commit: 583348bd65ceaf4a5067a6267dd236929e1b4b37
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-02-07 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 9:28 [PATCH 0/4] ASoC: SOF: Improve the spcm and ipc4 copier prints Peter Ujfalusi
2025-02-06 9:28 ` [PATCH 1/4] ASoC: SOF: Relocate and rework functionality for PCM stream freeing Peter Ujfalusi
2025-02-06 9:28 ` [PATCH 2/4] ASoC: SOF: pcm: Move period/buffer configuration print after platform open Peter Ujfalusi
2025-02-06 9:28 ` [PATCH 3/4] ASoC: SOF: pcm: Add snd_sof_pcm specific wrappers for dev_dbg() and dev_err() Peter Ujfalusi
2025-02-06 9:28 ` [PATCH 4/4] ASoC: SOF: ipc4-topology: Improve the information in prepare_copier prints Peter Ujfalusi
2025-02-07 14:02 ` 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=173893696397.35212.580149591364875425.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.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