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 updates for v6.5
Date: Mon, 26 Jun 2023 16:00:31 +0200	[thread overview]
Message-ID: <871qhygw74.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230626133249.DC126C433C8@smtp.kernel.org>

On Mon, 26 Jun 2023 15:32:40 +0200,
Mark Brown wrote:
> 
> The following changes since commit 1f1ef7e5bbe2de125da413e238915f6047ea4ba2:
> 
>   ASoC: intel: sof_sdw: Fixup typo in device link checking (2023-06-19 12:58:22 +0100)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-v6.5
> 
> for you to fetch changes up to 2d0cad0473bd1ffbc5842be0b9f2546265acb011:
> 
>   ASoC: core: Always store of_node when getting DAI link component (2023-06-23 22:09:00 +0100)
> 
> ----------------------------------------------------------------
> ASoC: Updates for v6.5
> 
> A fairly quiet release from a core and framework point of view, but a
> very big one from the point of view of new drivers:
> 
>  - More refectoring from Morimoto-san, this time mainly around DAI
>    links and how we control the ordering of trigger() callbacks.
>  - Convert a lot of drivers to use maple tree based caches.
>  - Lots of work on the x86 driver stack.
>  - Compressed audio support for Qualcomm.
>  - Support for AMD SoundWire, Analog Devices SSM3515, Google Chameleon,
>    Ingenic X1000, Intel systems with various CODECs, Longsoon platforms,
>    Maxim MAX98388, Mediatek MT8188, Nuvoton NAU8825C, NXP platforms with
>    NAU8822, Qualcomm WSA884x, StarFive JH7110, Texas Instruments TAS2781.

Pulled now.  Thanks.


Takashi

      reply	other threads:[~2023-06-26 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 13:32 [GIT PULL] ASoC updates for v6.5 Mark Brown
2023-06-26 14:00 ` 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=871qhygw74.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