Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	 patches@opensource.cirrus.com
Subject: Re: [PATCH] firmware: cs_dsp: rate-limit log messages in KUnit builds
Date: Tue, 03 Feb 2026 12:05:19 +0000	[thread overview]
Message-ID: <177012031931.85387.7521440900629176229.b4-ty@kernel.org> (raw)
In-Reply-To: <20260130171256.863152-1-rf@opensource.cirrus.com>

On Fri, 30 Jan 2026 17:12:56 +0000, Richard Fitzgerald wrote:
> Use the dev_*_ratelimit() macros if the cs_dsp KUnit tests are enabled
> in the build, and allow the KUnit tests to disable message output.
> 
> Some of the KUnit tests cause a very large number of log messages from
> cs_dsp, because the tests perform many different test cases. This could
> cause some lines to be dropped from the kernel log. Dropped lines can
> prevent the KUnit wrappers from parsing the ktap output in the dmesg log.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] firmware: cs_dsp: rate-limit log messages in KUnit builds
      commit: 10db9f6899dd3a2dfd26efd40afd308891dc44a8

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


      reply	other threads:[~2026-02-03 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 17:12 [PATCH] firmware: cs_dsp: rate-limit log messages in KUnit builds Richard Fitzgerald
2026-02-03 12:05 ` 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=177012031931.85387.7521440900629176229.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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