All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Gregory Clement <gregory.clement@bootlin.com>,
	arm-soc <arm@kernel.org>,
	Device Tree <devicetree@vger.kernel.org>
Subject: Re: [PATCH 08/11] DT: mtd: Convert orion-nand to YAML
Date: Mon, 22 Aug 2022 08:43:32 -0500	[thread overview]
Message-ID: <20220822134332.GA3732690-robh@kernel.org> (raw)
In-Reply-To: <YwLSU/DH7UrSPorH@lunn.ch>

On Mon, Aug 22, 2022 at 02:48:19AM +0200, Andrew Lunn wrote:
> On Sun, Aug 21, 2022 at 03:21:26PM -0500, Rob Herring wrote:
> > On Sat, 20 Aug 2022 21:48:01 +0200, Andrew Lunn wrote:
> > > This works for Kirkwood, but orion5x has an odd bus structure
> > > which results in some warnings.
> > > 
> > > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > > ---
> > >  .../bindings/mtd/marvell,orion-nand.yaml      | 85 +++++++++++++++++++
> > >  .../devicetree/bindings/mtd/orion-nand.txt    | 50 -----------
> > >  2 files changed, 85 insertions(+), 50 deletions(-)
> > >  create mode 100644 Documentation/devicetree/bindings/mtd/marvell,orion-nand.yaml
> > >  delete mode 100644 Documentation/devicetree/bindings/mtd/orion-nand.txt
> > > 
> > 
> > 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:
> > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mtd/marvell,orion-nand.example.dtb: nand-controller@f4000000: #size-cells:0:0: 0 was expected
> > 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mtd/nand-controller.yaml
> > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mtd/marvell,orion-nand.example.dtb: nand-controller@f4000000: #size-cells:0:0: 0 was expected
> > 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mtd/marvell,orion-nand.yaml
> 
> Does the bot not apply patches N-1 before testing patch N? In this
> case, if patch N-2 was applied, you would not see this warning.

It does unless there is a failure and it drops the prior patches.

Rob

  reply	other threads:[~2022-08-22 13:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20 19:47 [PATCH 00/11] Start converting MVEBU bindings to YAML Andrew Lunn
2022-08-20 19:47 ` [PATCH 01/11] DT: RTC: orion-rtc: Convert " Andrew Lunn
2022-08-22 20:49   ` Rob Herring
2022-08-22 20:55   ` Rob Herring
2022-08-20 19:47 ` [PATCH 02/11] DT: thermal: marvell,kirkwood-thermal: " Andrew Lunn
2022-08-20 19:47 ` [PATCH 03/11] DT: pinctrl: Convert marvell,kirkwood-pintctrl " Andrew Lunn
2022-08-22 21:16   ` Rob Herring
2022-08-20 19:47 ` [PATCH 04/11] DT: USB: Convert ehci-orion " Andrew Lunn
2022-08-21 20:21   ` Rob Herring
2022-08-20 19:47 ` [PATCH 05/11] DT: watchdog: Convert marvel.txt " Andrew Lunn
2022-08-21 20:21   ` Rob Herring
2022-08-22  0:20     ` Andrew Lunn
2022-08-22 13:47       ` Rob Herring
2022-08-20 19:47 ` [PATCH 06/11] arm: DT: kirkwood/orion5: Rename watchdog node Andrew Lunn
2022-08-20 19:48 ` [PATCH 07/11] DT: nand-controller: Reflect reality of marvell,orion-nand Andrew Lunn
2022-08-21 20:21   ` Rob Herring
2022-08-20 19:48 ` [PATCH 08/11] DT: mtd: Convert orion-nand to YAML Andrew Lunn
2022-08-21 20:21   ` Rob Herring
2022-08-22  0:48     ` Andrew Lunn
2022-08-22 13:43       ` Rob Herring [this message]
2022-08-20 19:48 ` [PATCH 09/11] arm: DT: kirkwood.dtsi: Rename nand to nand-controller Andrew Lunn
2022-08-20 19:48 ` [PATCH 10/11] DT: timer: Convert marvell,orion-timer.txt to YAML Andrew Lunn
2022-08-20 19:48 ` [PATCH 11/11] DT: clock: Convert mvebu-gated-clock.txt " Andrew Lunn
2022-08-22 13:49 ` [PATCH 00/11] Start converting MVEBU bindings " Rob Herring
2022-08-22 13:53 ` Rob Herring
2022-08-22 14:28   ` Andrew Lunn
2022-08-30 18:58     ` 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=20220822134332.GA3732690-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=arm@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.