From: Takashi Iwai <tiwai@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] sound fixes for 6.1-rc8
Date: Fri, 02 Dec 2022 09:46:56 +0100 [thread overview]
Message-ID: <87mt86kxa7.wl-tiwai@suse.de> (raw)
Linus,
please pull sound fixes for v6.1-rc8 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-6.1-rc8
The topmost commit is b47068b4aa53a57552398e3f60d0ed1918700c2b
----------------------------------------------------------------
sound fixes for 6.1-rc8
Likely the last piece for 6.1; the only significant fixes are ASoC
core ops fixes, while others are device-specific (rather minor)
fixes in ASoC and FireWire drivers.
All appear safe enough to take as a late-stage material.
----------------------------------------------------------------
Charles Keepax (2):
ASoC: ops: Correct bounds check for second channel on SX controls
ASoC: cs42l51: Correct PGA Volume minimum value
Hui Tang (1):
ASoC: tlv320adc3xxx: Fix build error for implicit function declaration
Mark Brown (2):
ASoC: ops: Fix bounds check for _sx controls
ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx()
Shengjiu Wang (2):
ASoC: fsl_micfil: explicitly clear software reset bit
ASoC: fsl_micfil: explicitly clear CHnF flags
Takashi Sakamoto (1):
ALSA: dice: fix regression for Lexicon I-ONIX FW810S
---
sound/firewire/dice/dice-stream.c | 12 +++++++-----
sound/soc/codecs/cs42l51.c | 2 +-
sound/soc/codecs/tlv320adc3xxx.c | 3 +++
sound/soc/fsl/fsl_micfil.c | 19 +++++++++++++++++++
sound/soc/soc-ops.c | 11 ++++++++---
5 files changed, 38 insertions(+), 9 deletions(-)
next reply other threads:[~2022-12-02 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 8:46 Takashi Iwai [this message]
2022-12-02 23:45 ` [GIT PULL] sound fixes for 6.1-rc8 pr-tracker-bot
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=87mt86kxa7.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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