linux-kernel - Re: [PATCH v3 1/5] ASoC: cs35l45: Support for GPIO pins configuration.

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>] [day] [month] [year] [list]

Date:   Tue, 21 Mar 2023 16:51:03 +0000
From:   Mark Brown <broonie@...nel.org>
To:     James Schulman <james.schulman@...rus.com>,
        David Rhodes <david.rhodes@...rus.com>,
        Richard Fitzgerald <rf@...nsource.cirrus.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Rob Herring <robh+dt@...nel.org>,
        Vlad Karpovich <vkarpovi@...nsource.cirrus.com>
Cc:     alsa-devel@...a-project.org, patches@...nsource.cirrus.com,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v3 1/5] ASoC: cs35l45: Support for GPIO pins
 configuration.

On Wed, 15 Mar 2023 10:47:18 -0500, Vlad Karpovich wrote:
> Adds device tree configuration for cs35l45 GPIOs
> 
> 

Applied to

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

Thanks!

[1/5] ASoC: cs35l45: Support for GPIO pins configuration.
      commit: fa8c052b4c614aa1d2d60e5c9f40e9d885bf9511
[2/5] ASoC: dt-bindings: cs35l45: GPIOs configuration
      commit: c6cec088ab037b57e08e0694e2b150b1b034826c
[3/5] ASoC: cs35l45: IRQ support
      commit: 6085f9e6dc1973cf98ee7f5dcf629939e50f1b84
[4/5] ASoC: cs35l45: DSP Support
      commit: 74b14e2850a34740c121cf2758d4181063d4c77c
[5/5] ASoC: cs35l45: Hibernation support
      commit: 6c07be8fe92c6b0c24ee1c599601dce3506b83c7

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