From: Mark Brown <broonie@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
matthias.bgg@gmail.com, linux-spi@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
arinc.unal@arinc9.com
Subject: Re: [RESEND PATCH v3] dt-bindings: spi: migrate mt7621 text bindings to YAML
Date: Tue, 27 Sep 2022 13:48:32 +0100 [thread overview]
Message-ID: <166428291253.354496.654801731263989122.b4-ty@kernel.org> (raw)
In-Reply-To: <20220927031929.807070-1-sergio.paracuellos@gmail.com>
On Tue, 27 Sep 2022 05:19:29 +0200, Sergio Paracuellos wrote:
> SoC MT7621 SPI bindings used text format, so migrate them to YAML.
> There are some additions to the binding that were not in the original
> file. This binding is used in MT7621 and MT7628a Ralink SoCs. To
> properly match both dts nodes in tree we need to add to the schema
> 'clocks', 'clock-names' and 'reset-names'. Both 'clock-names' and
> 'reset-names' use 'spi' as string so maintain that as const in
> the schema.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] dt-bindings: spi: migrate mt7621 text bindings to YAML
commit: 048f71f7685706dcc859160cc74f73e361cfe6c0
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
prev parent reply other threads:[~2022-09-27 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 3:19 [RESEND PATCH v3] dt-bindings: spi: migrate mt7621 text bindings to YAML Sergio Paracuellos
2022-09-27 11:12 ` Mark Brown
2022-09-27 11:36 ` Sergio Paracuellos
2022-09-27 11:59 ` Mark Brown
2022-09-27 12:09 ` Sergio Paracuellos
2022-09-29 16:48 ` Rob Herring
2022-09-29 17:22 ` Sergio Paracuellos
2022-09-27 12:48 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=166428291253.354496.654801731263989122.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox