Linux Sound subsystem development
 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 v7.3-merge-window
Date: Thu, 27 Aug 2026 16:21:57 +0200	[thread overview]
Message-ID: <87zey7ej96.wl-tiwai@suse.de> (raw)
In-Reply-To: <b334f5b2d0e7c0c73107f54bfee509b1@kernel.org>

On Thu, 27 Aug 2026 15:22:59 +0200,
Mark Brown wrote:
> 
> The following changes since commit 0c7aeb0f5eceb95b5887bd8e83fef865e5a49a13:
> 
>   ASoC: tas2783-sdw: do not treat read-only Controls as writable (2026-08-14 16:20:47 +0100)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v7.3-merge-window
> 
> for you to fetch changes up to 15596a87fcc6fa07a162858e5fd00ba31752096b:
> 
>   ASoC: amd: acp-config: change quirks to cover all ASUS FA401EA variants (2026-08-27 00:15:37 +0100)
> 
> ----------------------------------------------------------------
> ASoC: Fixes for v7.3
> 
> A fairly big batch of fixes that came in during the merge window.
> There's a lot of quirks for x86 systems and a bunch of driver specific
> fixes, the most critical being the fixes for Tegra's register
> definitions.  It turned out that they had been relying on the regmap
> default handling bugs that were fixed in v7.2 and so audio was fairly
> badly broken, unfortunately the issue wasn't noticed in time for
> release.

Pulled now.  Thanks.


Takashi

      reply	other threads:[~2026-08-27 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 13:22 [GIT PULL] ASoC fixes for v7.3-merge-window Mark Brown
2026-08-27 14:21 ` 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=87zey7ej96.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