All of 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.7
Date: Sat, 21 Oct 2023 09:56:45 +0200	[thread overview]
Message-ID: <87h6mkif2a.wl-tiwai@suse.de> (raw)
In-Reply-To: <20231020212909.268F5C433C7@smtp.kernel.org>

On Fri, 20 Oct 2023 23:28:58 +0200,
Mark Brown wrote:
> 
> The following changes since commit 99d426c6dd2d6f9734617ec12def856ee35b9218:
> 
>   ASoC: cs42l43: Update values for bias sense (2023-10-10 12:50:40 +0100)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-v6.7
> 
> for you to fetch changes up to 45f1b12e0366a750d65e92307685964488a3b6f4:
> 
>   ASoC: Intel: more machine driver updates for 6.7 (2023-10-19 21:02:18 +0100)
> 
> ----------------------------------------------------------------
> ASoC: Updates for v6.7
> 
> This is quite a large set of changes but mostly due to API cleanups and
> in driver specific ways rather than due to anything subsystem wide.
> Highlights include:
> 
>  - Standardisation of API prefixes on snd_soc_, removing asoc_.
>  - GPIO API usage improvements.
>  - Support for HDA patches.
>  - Lots of work on SOF, including crash dump support.
>  - Support for AMD platforms with es83xx, Awinc AT87390, many Intel
>    platforms, many Mediatek platforms, Qualcomm SM6115,  Richtek RTQ9128
>    and Texas Instruments TAS575x.

Thanks, pulled now.

Now we can apply a cleanup to make the remaining remove_late callback
void.  I'm going to submit the patch later.


Takashi

      reply	other threads:[~2023-10-21  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 21:28 [GIT PULL] ASoC updates for v6.7 Mark Brown
2023-10-21  7:56 ` 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=87h6mkif2a.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 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.