From: Conor Dooley <conor.dooley@microchip.com>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: Lucas Tanure <tanure@linux.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Yixun Lan <dlan@gentoo.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.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 09:11:47 +0100 [thread overview]
Message-ID: <20230621-sloppy-lisp-d6569b907c41@wendy> (raw)
In-Reply-To: <6fe5dfb6-5f18-feca-a2e7-8cfb78627e01@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
On Wed, Jun 21, 2023 at 10:04:28AM +0200, Neil Armstrong wrote:
> On 21/06/2023 10:01, Conor Dooley wrote:
> > Aye, but we do not want to propagate that. New stuff should not be
> > adding undocumented compatibles, and those that are undocumented should
> > be documented.
>
> Documentation is ongoing, it takes time !
Don't worry, I wasn't trying to criticise, just pointing out the ideal
situation.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-21 8:12 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 [this message]
2023-06-21 8:06 ` Krzysztof Kozlowski
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=20230621-sloppy-lisp-d6569b907c41@wendy \
--to=conor.dooley@microchip.com \
--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=krzysztof.kozlowski@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;
as well as URLs for NNTP newsgroup(s).