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.18-rc2
Date: Thu, 30 Oct 2025 13:15:02 +0100 [thread overview]
Message-ID: <87tszg37sp.wl-tiwai@suse.de> (raw)
In-Reply-To: <741e6973e073ce0ea4f6e17d7b1b080e@kernel.org>
On Thu, 30 Oct 2025 12:33:11 +0100,
Mark Brown wrote:
>
> The following changes since commit 211ddde0823f1442e4ad052a2f30f050145ccada:
>
> Linux 6.18-rc2 (2025-10-19 15:19:16 -1000)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v6.18-rc2
>
> for you to fetch changes up to 5e5c8aa73d99f1daa9f2ec1474b7fc1a6952764b:
>
> ASoC: dt-bindings: pm4125-sdw: correct number of soundwire ports (2025-10-29 14:54:47 +0000)
>
> ----------------------------------------------------------------
> ASoC: Fixes for v6.18
>
> A bigger batch of fixes than I'd like, things built up due to holidays
> and some last minute issues which caused me to hold off on sending a pul
> request. None of these are super remarkable, and there's a few new
> device IDs in here too including a relatively big block of AMD devices.
>
> The Cirrus Logic CS530x support subject line is actually a fix that was
> on the start of that series and got pulled in here, I forgot to fix the
> subject up when merging.
Pulled now. Thanks.
Takashi
prev parent reply other threads:[~2025-10-30 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 11:33 [GIT PULL] ASoC fixes for v6.18-rc2 Mark Brown
2025-10-30 12:15 ` 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=87tszg37sp.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.