public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [GIT PULL] ASoC fixes for v5.18-rc4
Date: Sun, 08 May 2022 11:04:55 +0200	[thread overview]
Message-ID: <s5h7d6wo0nc.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220428111823.D6F52C385A0@smtp.kernel.org>

On Thu, 28 Apr 2022 13:18:13 +0200,
Mark Brown wrote:
> 
> The following changes since commit 5b933c7262c5b0ea11ea3c3b3ea81add04895954:
> 
>   firmware: cs_dsp: Fix overrun of unterminated control name string (2022-04-12 17:57:04 +0100)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v5.18-rc4
> 
> for you to fetch changes up to c61711c1c95791850be48dd65a1d72eb34ba719f:
> 
>   ASoC: SOF: Fix NULL pointer exception in sof_pci_probe callback (2022-04-27 14:15:21 +0100)
> 
> ----------------------------------------------------------------
> ASoC: Fixes for v5.18
> 
> A larger collection of fixes than I'd like, mainly because mixer-test
> is making it's way into the CI systems and turning up issues on a wider
> range of systems.  The most substantial thing though is a revert and an
> alternative fix for a dmaengine issue where the fix caused disruption
> for some other configurations, the core fix is backed out an a driver
> specific thing done instead.

Now merged.  Sorry for the delayed action, I've been off in the last
weeks.

I'm going to send a PR today, so that it'll be hopefully included in
rc6.


thanks,

Takashi -- slowly digesting

      reply	other threads:[~2022-05-08  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 11:18 [GIT PULL] ASoC fixes for v5.18-rc4 Mark Brown
2022-05-08  9:04 ` 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=s5h7d6wo0nc.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