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 updates for v6.17
Date: Thu, 24 Jul 2025 14:33:23 +0200 [thread overview]
Message-ID: <87y0sdkbu4.wl-tiwai@suse.de> (raw)
In-Reply-To: <492f6d2b51bc6aeeda03fb8ac85ee34a.broonie@kernel.org>
On Thu, 24 Jul 2025 13:42:08 +0200,
Mark Brown wrote:
>
> The following changes since commit 347e9f5043c89695b01e66b3ed111755afcf1911:
>
> Linux 6.16-rc6 (2025-07-13 14:25:58 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-v6.17
>
> for you to fetch changes up to c58c35ef6ae62e36927f506a5afc66610b7261d9:
>
> ASoC: qcom: sm8250: Add Fairphone 4 soundcard compatible (2025-07-23 15:09:30 +0100)
>
> ----------------------------------------------------------------
> ASoC: Updates for v6.17
>
> There's a few new drivers here and quite a lot of cleanup work from
> Morimoto-san but generally this has been quite a quiet release,
> resulting in a fairly small diffstat. Highlights include:
>
> - Refactoring of the Kconfig menus to be hopefully more consistant and
> easier to navigate.
> - Refactoring of the DAPM code, mainly hiding functionality that
> doesn't need to be exposed to drivers.
> - Removal of the unused upstream weak paths DAPM functionality.
> - Further work on the generic handling for SoundWire SDCA devices.
> - Cleanups of our usage of the PM autosuspend functions, this pulls in
> some PM core changes on a shared tag.
> - Support for AMD ACP7.2 and SoundWire on ACP 7.1, Fairphone 4 & 5,
> various Intel systems, Qualcomm QCS8275, Richtek RTQ9124 and TI TAS5753.
Pulled now. Thanks.
Takashi
prev parent reply other threads:[~2025-07-24 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 11:42 [GIT PULL] ASoC updates for v6.17 Mark Brown
2025-07-24 12:33 ` 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=87y0sdkbu4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.