linux-kernel - Re: [PATCH v6 00/13] Add support for IIO devices in ASoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 12 Jul 2023 12:46:40 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Jonathan Cameron <jic23@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Herve Codina <herve.codina@...tlin.com>
Cc:     alsa-devel@...a-project.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
        Wojciech Ziemba <wojciech.ziemba@...el.com>,
        Christophe Leroy <christophe.leroy@...roup.eu>,
        Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH v6 00/13] Add support for IIO devices in ASoC

On Fri, 23 Jun 2023 10:58:17 +0200, Herve Codina wrote:
> Several weeks ago, I sent a series [1] for adding a potentiometer as an
> auxiliary device in ASoC. The feedback was that the potentiometer should
> be directly handled in IIO (as other potentiometers) and something more
> generic should be present in ASoC in order to have a binding to import
> some IIO devices into sound cards.
> 
> The series related to the IIO potentiometer device is already applied.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[01/13] ASoC: dt-bindings: Add audio-iio-aux
        commit: cacff5e8a305b98595829ac4f5fe669e015ce19c
[02/13] ASoC: dt-bindings: simple-card: Add additional-devs subnode
        commit: b5f3484117b86cb128f500ff2d730c3cfcb9ddfc
[03/13] iio: inkern: Check error explicitly in iio_channel_read_max()
        commit: f75c544d74133278b004195220f540d8ab953e14
[04/13] iio: consumer.h: Fix raw values documentation notes
        commit: 1e1b4fbd6d0f8c54af14dcf18bd3136816153b12
[05/13] iio: inkern: Remove the 'unused' variable usage in iio_channel_read_max()
        commit: ad4e8480a1db8713ee7dfcc2770ea9f577750111
[06/13] iio: inkern: Fix headers inclusion order
        commit: 524cfdf6b88e2536f90f726b8c01ffe218f37d68
[07/13] minmax: Introduce {min,max}_array()
        commit: c952c748c7a983a8bda9112984e6f2c1f6e441a5
[08/13] iio: inkern: Use max_array() to get the maximum value from an array
        commit: 97aee7157eeadaf628e7f76da5e49cee91f19901
[09/13] iio: inkern: Replace a FIXME comment by a TODO one
        commit: 4dc603735826ec3963e30d6f25260255ca96d103
[10/13] iio: inkern: Add a helper to query an available minimum raw value
        commit: 7560418078b939e1e83f7dce502ec3c1ca8c152f
[11/13] ASoC: soc-dapm.h: Convert macros to return a compound literal
        commit: 12e58fec5b2aff3ae6fef4e6c278f295a666b9b6
[12/13] ASoC: codecs: Add support for the generic IIO auxiliary devices
        commit: 1d298ad822178d365b53eac298c1752730505306
[13/13] ASoC: simple-card: Handle additional devices
        commit: 6d8ad35d119ca4c9c6fdf83faa733102c4a63f4b

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark