linux-kernel - Re: [PATCH v2 0/5] ASoC: Convert remaining Realtek codecs to GPIO descriptors

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 for Android: free password hash cracker in your pocket

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

Message-Id: <169231179901.153247.7284114933332973208.b4-ty@kernel.org>
Date:   Thu, 17 Aug 2023 23:36:39 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Oder Chiou <oder_chiou@...ltek.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Linus Walleij <linus.walleij@...aro.org>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/5] ASoC: Convert remaining Realtek codecs to GPIO
 descriptors

On Thu, 17 Aug 2023 16:03:16 +0200, Linus Walleij wrote:
> After dropping unused headers a few Realtek devices
> actually using the GPIO descriptors remain.
> 
> Converting them to use optional GPIO descriptors is
> pretty straight-forward.
> 
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: rt5640: Convert to just use GPIO descriptors
      commit: a9b5f21073c0c687068f17e23385ec43fc643b08
[2/5] ASoC: rt5665: Convert to use GPIO descriptors
      commit: 647a3c4c33cd2c3902cdc07c50f3129166d715f5
[3/5] ASoC: rt5668: Convert to use GPIO descriptors
      commit: ab2a5d17064436585807f2ece5e6b4b03769a11f
[4/5] ASoC: rt5682: Convert to use GPIO descriptors
      commit: ed11701751d43fb2318c625e65e0507b5234f8a5
[5/5] ASoC: rt5682s: Convert to use GPIO descriptors
      commit: 8793bee716452e5e2f9bf085fbe01f9e3d1e659f

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