[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173626654806.139336.10060556793703295890.b4-ty@kernel.org>
Date: Tue, 07 Jan 2025 16:15:48 +0000
From: Mark Brown <broonie@...nel.org>
To: Lars-Peter Clausen <lars@...afoo.de>,
Nuno Sá <nuno.sa@...log.com>,
Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Shenghao Ding <shenghao-ding@...com>,
Kevin Lu <kevin-lu@...com>, Baojun Xu <baojun.xu@...com>,
Neil Armstrong <neil.armstrong@...aro.org>,
Shengjiu Wang <shengjiu.wang@....com>, Viorel Suman <viorel.suman@....com>,
Daniele Alessandrelli <daniele.alessandrelli@...el.com>,
"Paul J. Murphy" <paul.j.murphy@...el.com>,
Igor Prusov <ivprusov@...utedevices.com>, Andrew Davis <afd@...com>,
Shi Fu <shifu0704@...ndersoft.com>, linux-sound@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH] ASoC: dt-bindings: Correct indentation and style in
DTS example
On Tue, 07 Jan 2025 13:58:58 +0100, Krzysztof Kozlowski wrote:
> DTS example in the bindings should be indented with 2- or 4-spaces and
> aligned with opening '- |', so correct any differences like 3-spaces or
> mixtures 2- and 4-spaces in one binding. While touching the lines do
> other non-functional changes: replace raw number with proper define for
> GPIO flag and use generic node name.
>
> No functional changes here, but saves some comments during reviews of
> new patches built on existing code.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: dt-bindings: Correct indentation and style in DTS example
commit: fffe003fc209a3c1f3d07be7e860fed4e51c4c00
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