devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: David Bauer <mail@david-bauer.net>,
	lgirdwood@gmail.com, broonie@kernel.org,
	 linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	 AngeloGioacchino Del Regno
	<angelogioacchino.delregno@somainline.org>
Subject: Re: [PATCH v6 1/2] dt-bindings: pinctrl: Add bindings for Awinic AW9523/AW9523B
Date: Tue, 5 Mar 2024 23:25:09 +0100	[thread overview]
Message-ID: <CACRpkdY2jfszTNvUHxc8-AXFwZKQaaOkcTwZrAiKi2rU5tTn6g@mail.gmail.com> (raw)
In-Reply-To: <CAL_Jsq+sHy=mr0paWvxOL8yT9TwuaJdfapX0sFkOJFtjCqoT1w@mail.gmail.com>

On Tue, Mar 5, 2024 at 6:28 PM Rob Herring <robh+dt@kernel.org> wrote:

> Linus, did you just apply this 3 year old bit-rotted patch? Linux-next
> now warns:

Not "just", I did run checks on it first i.e.:
$ make DT_SCHEMA_FILES=Documentation/devicetree/bindings/pinctrl/awinic,aw9523-pinctrl.yaml
dt_binding_check
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/dtc/dtc.o
  HOSTCC  scripts/dtc/flattree.o
  HOSTCC  scripts/dtc/fstree.o
  HOSTCC  scripts/dtc/data.o
  HOSTCC  scripts/dtc/livetree.o
  HOSTCC  scripts/dtc/treesource.o
  HOSTCC  scripts/dtc/srcpos.o
  HOSTCC  scripts/dtc/checks.o
  HOSTCC  scripts/dtc/util.o
  LEX     scripts/dtc/dtc-lexer.lex.c
  YACC    scripts/dtc/dtc-parser.tab.[ch]
  HOSTCC  scripts/dtc/dtc-lexer.lex.o
  HOSTCC  scripts/dtc/dtc-parser.tab.o
  HOSTLD  scripts/dtc/dtc
  LINT    Documentation/devicetree/bindings
usage: yamllint [-h] [-] [-c CONFIG_FILE | -d CONFIG_DATA] [-f
{parsable,standard,colored,github,auto}] [-s] [--no-warnings] [-v]
[FILE_OR_DIR ...]
yamllint: error: one of the arguments FILE_OR_DIR - is required
  CHKDT   Documentation/devicetree/bindings/processed-schema.json
  SCHEMA  Documentation/devicetree/bindings/processed-schema.json

So that's at least something but apparently not enough, hm the yamllint moaning
should be a hint should it not... it's on v6.8-rc1.

> ./Documentation/devicetree/bindings/pinctrl/awinic,aw9523-pinctrl.yaml:49:2:
> [error] missing starting space in comment (comments)
> ./Documentation/devicetree/bindings/pinctrl/awinic,aw9523-pinctrl.yaml:56:11:
> [error] string value is redundantly quoted with any quotes
> (quoted-strings)

They were so simple that I just fixed them up in-tree.

> Also, David's S-o-b is missing if you picked up this one.

I mailed David about it.

Yours,
Linus Walleij

  reply	other threads:[~2024-03-05 22:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 21:44 [PATCH v6 1/2] dt-bindings: pinctrl: Add bindings for Awinic AW9523/AW9523B David Bauer
2021-06-24 21:44 ` [PATCH v6 2/2] pinctrl: Add driver for Awinic AW9523/B I2C GPIO Expander David Bauer
2021-06-25  4:50   ` kernel test robot
2021-07-23 16:09     ` Linus Walleij
2021-06-25  6:08   ` kernel test robot
2024-03-05 17:27 ` [PATCH v6 1/2] dt-bindings: pinctrl: Add bindings for Awinic AW9523/AW9523B Rob Herring
2024-03-05 22:25   ` Linus Walleij [this message]
2024-03-06 13:20     ` Rob Herring

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=CACRpkdY2jfszTNvUHxc8-AXFwZKQaaOkcTwZrAiKi2rU5tTn6g@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=angelogioacchino.delregno@somainline.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mail@david-bauer.net \
    --cc=robh+dt@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).