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.17-rc7
Date: Thu, 10 Mar 2022 14:35:21 +0100 [thread overview]
Message-ID: <s5hfsnqexra.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220310121304.2F301C340EB@smtp.kernel.org>
On Thu, 10 Mar 2022 13:12:55 +0100,
Mark Brown wrote:
>
> The following changes since commit c5487b9cdea5c1ede38a7ec94db0fc59963c8e86:
>
> ASoC: cs4265: Fix the duplicated control name (2022-02-16 16:34:16 +0000)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v5.17-rc7
>
> for you to fetch changes up to 5e02fb590e83684f63217f93a9cdeabd6a925f9c:
>
> ASoC: cs35l41: Fix DSP mbox start command and global enable order (2022-03-07 13:12:38 +0000)
>
> ----------------------------------------------------------------
> ASoC: Potential fixes for v5.17
>
> Rather more fixes here than I'm comfortable with, we've had several
> vendors noticing issues late in the release cycle all of which are valid
> and reasonable fixes but it adds up to a much larger change set than I'd
> like. Several of the AMD fixes look like cleanups from the subject
> lines but are actually fixing user visible problems as well.
>
> If you were to merge this for 5.18 rather than 5.17 it wouldn't be the
> end of the world, stable will probably backport everything anyway.
Thanks, pulled now.
I had a few pending fixes but thought to push for 5.18, as those
weren't urgent. This PR also looks like non-urgent fixes, so I'm
inclined to wait for 5.18 merge for now. Let's see.
Takashi
prev parent reply other threads:[~2022-03-10 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 12:12 [GIT PULL] ASoC fixes for v5.17-rc7 Mark Brown
2022-03-10 13:35 ` 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=s5hfsnqexra.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.