[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170861150977.56623.15929903004855832989.b4-ty@kernel.org>
Date: Thu, 22 Feb 2024 14:18:29 +0000
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Banajit Goswami <bgoswami@...cinc.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Frank Rowand <frowand.list@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
linux-arm-msm@...r.kernel.org, linux-sound@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Chris Packham <chris.packham@...iedtelesis.co.nz>,
Bartosz Golaszewski <brgl@...ev.pl>, Sean Anderson <sean.anderson@...o.com>
Subject: Re: (subset) [PATCH v6 0/6] reset: gpio: ASoC: shared GPIO resets
On Mon, 29 Jan 2024 12:52:10 +0100, Krzysztof Kozlowski wrote:
> Dependencies / Merging
> ======================
> 1. Depends on !GPIOLIB stub:
> https://lore.kernel.org/all/20240125081601.118051-3-krzysztof.kozlowski@linaro.org/
>
> 2. Patch #2 (cpufreq: do not open-code of_phandle_args_equal()) and patch #4
> (reset: Instantiate reset GPIO controller for shared reset-gpios) depend on OF
> change (patch #1).
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[5/6] ASoC: dt-bindings: qcom,wsa8840: Add reset-gpios for shared line
commit: 26c8a435fce6ef8d1dea39cc52b15cf36c7e986b
[6/6] ASoC: codecs: wsa884x: Allow sharing reset GPIO
commit: 0dae534c48239be0a99092e46e1baade0cf3e04a
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
Powered by blists - more mailing lists