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.9-rc6
Date: Wed, 01 May 2024 18:11:30 +0200	[thread overview]
Message-ID: <87bk5pldfx.wl-tiwai@suse.de> (raw)
In-Reply-To: <549018ebcc16eaa42ffac7fdc865feb8.broonie@kernel.org>

On Wed, 01 May 2024 16:07:49 +0200,
Mark Brown wrote:
> 
> The following changes since commit fec50db7033ea478773b159e0e2efb135270e3b7:
> 
>   Linux 6.9-rc3 (2024-04-07 13:22:46 -0700)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v6.9-rc6
> 
> for you to fetch changes up to c5782bb5468acf86d8ca8e161267e8d055fb4161:
> 
>   ASoC: meson: tdm fixes (2024-04-30 23:36:23 +0900)
> 
> ----------------------------------------------------------------
> ASoC: Fixes for v6.9
> 
> This is much larger than is ideal, partly due to your holiday but also
> due to several vendors having come in with relatively large fixes at
> similar times.  It's all driver specific stuff.
> 
> The meson fixes from Jerome fix some rare timing issues with blocking
> operations happening in triggers, plus the continuous clock support
> which fixes clocking for some platforms.  The SOF series from Peter
> builds to the fix to avoid spurious resets of ChainDMA which triggered
> errors in cleanup paths with both PulseAudio and PipeWire, and there's
> also some simple new debugfs files from Pierre which make support a lot
> eaiser.

Thanks, pulled now.


Takashi

      reply	other threads:[~2024-05-01 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 14:07 [GIT PULL] ASoC fixes for v6.9-rc6 Mark Brown
2024-05-01 16:11 ` 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=87bk5pldfx.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