From: kovalev@altlinux.org
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
u.kleine-koenig@pengutronix.de, a.firago@yadro.com,
sashal@kernel.org, zhuning0077@gmail.com, tiwai@suse.com,
perex@perex.cz, broonie@kernel.org, lgirdwood@gmail.com,
kovalev@altlinux.org
Subject: [PATCH 6.1.y 0/7] ASoC: codecs: es8326: fix support
Date: Tue, 30 Jan 2024 12:47:01 +0300 [thread overview]
Message-ID: <20240130094708.290485-1-kovalev@altlinux.org> (raw)
These patches were backported from v6.6 upstream and
are intended for 6.1.y stable kernel.
Patches have been successfully tested on the latest 6.1.75 kernel.
[PATCH 6.1.y 1/7] ASoC: codecs: es8326: Convert to i2c's .probe_new()
[PATCH 6.1.y 2/7] ASoC: codecs: ES8326: Add es8326_mute function
[PATCH 6.1.y 3/7] ASoC: codecs: ES8326: Change Hp_detect register names
[PATCH 6.1.y 4/7] ASoC: codecs: ES8326: Change Volatile Reg function
[PATCH 6.1.y 5/7] ASoC: codecs: ES8326: Fix power-up sequence
[PATCH 6.1.y 6/7] ASOC: codecs: ES8326: Add calibration support for
[PATCH 6.1.y 7/7] ASoC: codecs: ES8326: Update jact detection function
next reply other threads:[~2024-02-06 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 9:47 kovalev [this message]
2024-01-30 9:47 ` [PATCH 6.1.y 1/7] ASoC: codecs: es8326: Convert to i2c's .probe_new() kovalev
2024-01-30 11:13 ` Mark Brown
2024-01-30 9:47 ` [PATCH 6.1.y 2/7] ASoC: codecs: ES8326: Add es8326_mute function kovalev
2024-01-30 9:47 ` [PATCH 6.1.y 3/7] ASoC: codecs: ES8326: Change Hp_detect register names kovalev
2024-01-30 9:47 ` [PATCH 6.1.y 4/7] ASoC: codecs: ES8326: Change Volatile Reg function kovalev
2024-01-30 9:47 ` [PATCH 6.1.y 5/7] ASoC: codecs: ES8326: Fix power-up sequence kovalev
2024-01-30 9:47 ` [PATCH 6.1.y 6/7] ASOC: codecs: ES8326: Add calibration support for version_b kovalev
2024-01-30 9:47 ` [PATCH 6.1.y 7/7] ASoC: codecs: ES8326: Update jact detection function kovalev
2024-02-03 1:13 ` [PATCH 6.1.y 0/7] ASoC: codecs: es8326: fix support Greg KH
2024-02-13 14:54 ` Greg KH
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=20240130094708.290485-1-kovalev@altlinux.org \
--to=kovalev@altlinux.org \
--cc=a.firago@yadro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=zhuning0077@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.