linux-kernel - Re: [PATCH] ASoC: samsung: h1940_uda1380: include proepr GPIO consumer header

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]

Message-Id: <165641227908.254424.11381365474563768174.b4-ty@kernel.org>
Date:   Tue, 28 Jun 2022 11:31:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Takashi Iwai <tiwai@...e.com>, Arnd Bergmann <arnd@...db.de>,
        krzysztof.kozlowski@...aro.org,
        Liam Girdwood <lgirdwood@...il.com>,
        alsa-devel@...a-project.org, s.nawrocki@...sung.com,
        linux-kernel@...r.kernel.org, Jaroslav Kysela <perex@...ex.cz>
Subject: Re: [PATCH] ASoC: samsung: h1940_uda1380: include proepr GPIO consumer header

On Mon, 27 Jun 2022 16:19:00 +0200, Krzysztof Kozlowski wrote:
> h1940_uda1380 uses gpiod*/GPIOD* so it should include GPIO consumer
> header.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: samsung: h1940_uda1380: include proepr GPIO consumer header
      commit: bd10b0dafdcf0ec1677cad70101e1f97b9e28f2e

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