From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: tanure@linux.com
Cc: Yixun Lan <dlan@gentoo.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>, Nick <nick@khadas.com>,
Artem <art@khadas.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] arm64: dts: meson-t7-a311d2-khadas-vim4: add initial device-tree
Date: Wed, 21 Jun 2023 10:06:41 +0200 [thread overview]
Message-ID: <7d229fb0-b8f6-e629-cbad-0a3501bd9bfe@linaro.org> (raw)
In-Reply-To: <CAJX_Q+3im20qphOXzn-=58Kx4--ajbaF4P8BVvRcDcPXn1Qheg@mail.gmail.com>
On 21/06/2023 09:37, Lucas Tanure wrote:
>>
>> https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42
>>
>> Best regards,
>> Krzysztof
>>
> Hi, I did not understand the recommendation here.
> Can I add "amlogic,meson-t7-uart" without Documentation changes?
No, you cannot and checkpatch will ensure that.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-06-21 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 13:48 [PATCH v2 0/2] Add Amlogic A311D2 and Khadas Vim4 Board Support Lucas Tanure
2023-06-20 13:48 ` [PATCH v2 1/2] dt-bindings: arm: amlogic: add Amlogic A311D2 bindings Lucas Tanure
2023-06-20 13:48 ` [PATCH v2 2/2] arm64: dts: meson-t7-a311d2-khadas-vim4: add initial device-tree Lucas Tanure
2023-06-20 22:09 ` Yixun Lan
2023-06-21 6:02 ` Krzysztof Kozlowski
2023-06-21 7:37 ` Lucas Tanure
2023-06-21 8:01 ` Conor Dooley
2023-06-21 8:04 ` Neil Armstrong
2023-06-21 8:11 ` Conor Dooley
2023-06-21 8:06 ` Krzysztof Kozlowski [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=7d229fb0-b8f6-e629-cbad-0a3501bd9bfe@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=art@khadas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nick@khadas.com \
--cc=robh+dt@kernel.org \
--cc=tanure@linux.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
all inboxes | Powered by JetHome®