public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	linux-sound@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [GIT PULL] ASoC fixes for v6.19-rc8
Date: Wed, 04 Feb 2026 17:07:17 +0100	[thread overview]
Message-ID: <87343gebm2.wl-tiwai@suse.de> (raw)
In-Reply-To: <dea287404ba003dd74f4976e9141e0b0@kernel.org>

On Wed, 04 Feb 2026 16:54:36 +0100,
Mark Brown wrote:
> 
> The following changes since commit 213c4e51267fd825cd21a08a055450cac7e0b7fb:
> 
>   ASoC: Intel: sof_es8336: fix headphone GPIO logic inversion (2026-01-27 12:45:47 +0000)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v6.19-rc8
> 
> for you to fetch changes up to f514248727606b9087bc38a284ff686e0093abf1:
> 
>   ASoC: fsl_xcvr: fix missing lock in fsl_xcvr_mode_put() (2026-02-04 11:29:58 +0000)
> 
> ----------------------------------------------------------------
> ASoC: Fixes for v6.19
> 
> A bunch more small fixes here, plus some more of the constant stream of
> quirks.   The most notable change here is Richard's change to the cs_dsp
> code for the KUnit tests which is relatively large, mostly due to
> boilerplate.  The tests were triggering large numbers of error messages
> as part of verifying that problems with input data are appropriately
> detected which in turn caused runtime issues for the framework due to
> the performance impact of pushing the logging out, while the logging is
> valuable in normal operation it's basically useless while doing tests
> designed to trigger it so rate limiting is an appropriate fix.

Pulled now.  Thanks.


Takashi

      reply	other threads:[~2026-02-04 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 15:54 [GIT PULL] ASoC fixes for v6.19-rc8 Mark Brown
2026-02-04 16:07 ` Takashi Iwai [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=87343gebm2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    /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