Alsa-Devel Archive on lore.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>, alsa-devel@alsa-project.org
Subject: Re: [GIT PULL] ASoC fixes for v6.12-rc4
Date: Thu, 24 Oct 2024 08:22:09 +0200	[thread overview]
Message-ID: <87ldye10mm.wl-tiwai@suse.de> (raw)
In-Reply-To: <0db698090dd7ea59422ec8f778d20dba.broonie@kernel.org>

On Wed, 23 Oct 2024 23:44:38 +0200,
Mark Brown wrote:
> 
> The following changes since commit 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b:
> 
>   Linux 6.12-rc2 (2024-10-06 15:32:27 -0700)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v6.12-rc4
> 
> for you to fetch changes up to db7e59e6a39a4d3d54ca8197c796557e6d480b0d:
> 
>   ASoC: qcom: sc7280: Fix missing Soundwire runtime stream alloc (2024-10-22 21:00:38 +0100)
> 
> ----------------------------------------------------------------
> ASoC: Fixes for v6.12
> 
> An uncomfortably large set of fixes due to me not getting round to
> sending them for longer than I should due to travel and illness.  This
> is mostly smaller driver specific changes, but there are a couple of
> generic changes:
> 
>  - Bumping the minimal topology ABI we check for during validation, the
>    code had support for v4 removed previously but the update of the
>    define used for initial validation was missed.
>  - Fix the assumption that DAPM structs will be embedded in a component
>    which isn't true for card widgets when doing name comparisons, though
>    fortunately this is rarely triggered.
> 
> We've pulled in one Soundwire fix which was part of a larger series
> fixing cleanup issues in on Intel Soundwire systems.

Pulled now.  Thanks.


Takashi

      reply	other threads:[~2024-10-24  6:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 21:44 [GIT PULL] ASoC fixes for v6.12-rc4 Mark Brown
2024-10-24  6:22 ` 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=87ldye10mm.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.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