From: Mark Brown <broonie@kernel.org>
To: kovalev@altlinux.org
Cc: stable@vger.kernel.org, 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, lgirdwood@gmail.com
Subject: Re: [PATCH 6.1.y 1/7] ASoC: codecs: es8326: Convert to i2c's .probe_new()
Date: Tue, 30 Jan 2024 11:13:55 +0000 [thread overview]
Message-ID: <25386374-44e8-4b74-8803-2dcb0806f80d@sirena.org.uk> (raw)
In-Reply-To: <20240130094708.290485-2-kovalev@altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
On Tue, Jan 30, 2024 at 12:47:02PM +0300, kovalev@altlinux.org wrote:
> From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>
> Commit 784252bac835c831e10c48be633cd1ff0d697326 upstream.
>
> The probe function doesn't make use of the i2c_device_id * parameter so it
> can be trivially converted.
This is obviously not a bug fix.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-01-30 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 9:47 [PATCH 6.1.y 0/7] ASoC: codecs: es8326: fix support kovalev
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 [this message]
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=25386374-44e8-4b74-8803-2dcb0806f80d@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a.firago@yadro.com \
--cc=alsa-devel@alsa-project.org \
--cc=kovalev@altlinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).