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: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [GIT PULL] ASoC fixes for v6.2-rc3
Date: Thu, 12 Jan 2023 14:02:35 +0100	[thread overview]
Message-ID: <878ri77vo4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230112113253.86989C433EF@smtp.kernel.org>

On Thu, 12 Jan 2023 12:32:35 +0100,
Mark Brown wrote:
> 
> The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
> 
>   Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v6.2-rc3
> 
> for you to fetch changes up to 242fc66ae6e1e2b8519daacc7590a73cd0e8a6e4:
> 
>   ASoC: fsl-asoc-card: Fix naming of AC'97 CODEC widgets (2023-01-10 12:45:22 +0000)
> 
> ----------------------------------------------------------------
> ASoC: Fixes for v6.2
> 
> There's quite a few fixes here, mostly board specific apart from the SOF
> power management ones.  We also have some new quirks and Kconfig tweaks
> to enable existing code on new platforms, and a one liner which exposes
> the SOF firmware state in debugfs to aid with debugging.
> 
> There's also a SPI fix that I mistakenly put in the wrong queue and
> did some merges on top of before I noticed, it seemed more trouble than
> it was worth to unpick things.  A copy of the same patch is also in the
> spi tree.

Thanks, pulled now.


Takashi

      reply	other threads:[~2023-01-12 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 11:32 [GIT PULL] ASoC fixes for v6.2-rc3 Mark Brown
2023-01-12 13:02 ` 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=878ri77vo4.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