devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
	Jon Hunter <jonathanh@nvidia.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	Daniel Vetter <daniel@ffwll.ch>,
	linux-tegra@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 2/6] dt-bindings: reserved-memory: Support framebuffer reserved memory
Date: Mon, 05 Sep 2022 21:29:58 -0500	[thread overview]
Message-ID: <1662431398.296852.3334460.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220905163300.391692-3-thierry.reding@gmail.com>

On Mon, 05 Sep 2022 18:32:56 +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Document the "framebuffer" compatible string for reserved memory nodes
> to annotate reserved memory regions used for framebuffer carveouts.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
>  .../bindings/reserved-memory/framebuffer.yaml | 46 +++++++++++++++++++
>  1 file changed, 46 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml
> 

My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):

yamllint warnings/errors:

dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/reserved-memory/framebuffer.example.dts:18.16-23.11: Warning (chosen_node_is_root): /example-0/chosen: chosen node must be at root node

doc reference errors (make refcheckdocs):

See https://patchwork.ozlabs.org/patch/

This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.

If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:

pip3 install dtschema --upgrade

Please check and re-submit.


  reply	other threads:[~2022-09-06  2:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 16:32 [PATCH 0/6] drm/simpledrm: Support system memory framebuffers Thierry Reding
2022-09-05 16:32 ` [PATCH 1/6] dt-bindings: display: simple-framebuffer: " Thierry Reding
2022-09-05 16:32 ` [PATCH 2/6] dt-bindings: reserved-memory: Support framebuffer reserved memory Thierry Reding
2022-09-06  2:29   ` Rob Herring [this message]
2022-09-06 14:27   ` Rob Herring
2022-09-14 16:05     ` Thierry Reding
2022-09-05 16:32 ` [PATCH 3/6] drm/simpledrm: Add support for system memory framebuffers Thierry Reding
2022-09-24 11:43   ` kernel test robot
2022-09-05 16:32 ` [PATCH 4/6] drm/format-helper: Support the AB24 format Thierry Reding
2022-09-07  7:23   ` Thomas Zimmermann
2022-09-14 16:09     ` Thierry Reding
2022-09-05 16:32 ` [PATCH 5/6] drm/simpledrm: " Thierry Reding
2022-09-07  7:12   ` Thomas Zimmermann
2022-09-05 16:33 ` [PATCH 6/6] arm64: tegra: Add simple framebuffer on Jetson Xavier NX Thierry Reding

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=1662431398.296852.3334460.nullmailer@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).