linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hermes Zhang <Hermes.Zhang@axis.com>
To: Rob Herring <robh@kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	kernel <kernel@axis.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Dan Murphy <dmurphy@ti.com>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: RE: [PATCH v2] dt-binding: leds: Document leds-multi-gpio bindings
Date: Tue, 23 Mar 2021 04:27:57 +0000	[thread overview]
Message-ID: <424d3de97a154c6a9580f27347882413@XBOX01.axis.com> (raw)
In-Reply-To: <1616434698.344402.2887754.nullmailer@robh.at.kernel.org>

> -----Original Message-----
> From: Rob Herring <robh@kernel.org>
> Sent: 2021年3月23日 1:38
> My bot found errors running 'make dt_binding_check' on your patch:
> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> /builds/robherring/linux-dt-
> review/Documentation/devicetree/bindings/leds/leds-multi-
> gpio.example.dt.yaml: gpios-led: led-states: 'oneOf' conditional failed, one
> must be fixed:
> 	[[0, 1, 2, 3]] is too short
> 	[0, 1, 2, 3] is too long
> 	From schema: /builds/robherring/linux-dt-
> review/Documentation/devicetree/bindings/leds/leds-multi-gpio.yaml
> 

Hi Rob,

Thanks. Yes, now I can see the warning, but I could not understand what was wrong? Could you give some hint? 

Best Regards,
Hermes

  reply	other threads:[~2021-03-23  4:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22  9:18 [PATCH v2] dt-binding: leds: Document leds-multi-gpio bindings Hermes Zhang
2021-03-22 17:38 ` Rob Herring
2021-03-23  4:27   ` Hermes Zhang [this message]
2021-03-23 14:00     ` Rob Herring
2021-03-24  2:52       ` Hermes Zhang

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=424d3de97a154c6a9580f27347882413@XBOX01.axis.com \
    --to=hermes.zhang@axis.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    /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).