All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/5] Arm VExpress/Juno motherboard bus clean-ups
Date: Fri, 20 Aug 2021 01:25:39 +0200	[thread overview]
Message-ID: <CACRpkdavBq5vfvVQMJm-R32VP-FEO6j6L5pUGGCWEFSiN=tUDw@mail.gmail.com> (raw)
In-Reply-To: <20210819184239.1192395-1-robh@kernel.org>

On Thu, Aug 19, 2021 at 8:42 PM Rob Herring <robh@kernel.org> wrote:

> I noticed we once again have warnings on VExpress/Juno bus nodes as the
> simple-bus schema now expects child nodes to have a unit-address.
> Digging into this I noticed the arm,vexpress-juno.yaml schema is out of
> date and missing some properties (some of which are unused). I found the
> 'ranges' handling to be odd as well. This series fixes all those issues.

The series looks good to me. Thanks for fixing this up!
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	 "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/5] Arm VExpress/Juno motherboard bus clean-ups
Date: Fri, 20 Aug 2021 01:25:39 +0200	[thread overview]
Message-ID: <CACRpkdavBq5vfvVQMJm-R32VP-FEO6j6L5pUGGCWEFSiN=tUDw@mail.gmail.com> (raw)
In-Reply-To: <20210819184239.1192395-1-robh@kernel.org>

On Thu, Aug 19, 2021 at 8:42 PM Rob Herring <robh@kernel.org> wrote:

> I noticed we once again have warnings on VExpress/Juno bus nodes as the
> simple-bus schema now expects child nodes to have a unit-address.
> Digging into this I noticed the arm,vexpress-juno.yaml schema is out of
> date and missing some properties (some of which are unused). I found the
> 'ranges' handling to be odd as well. This series fixes all those issues.

The series looks good to me. Thanks for fixing this up!
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-08-19 23:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 18:42 [PATCH 0/5] Arm VExpress/Juno motherboard bus clean-ups Rob Herring
2021-08-19 18:42 ` Rob Herring
2021-08-19 18:42 ` [PATCH 1/5] dt-bindings: arm,vexpress-juno: Fix 'motherboard' node name Rob Herring
2021-08-19 18:42   ` [PATCH 1/5] dt-bindings: arm, vexpress-juno: " Rob Herring
2021-08-19 18:42 ` [PATCH 2/5] dt-bindings: arm,vexpress-juno: Add missing motherboard properties Rob Herring
2021-08-19 18:42   ` [PATCH 2/5] dt-bindings: arm, vexpress-juno: " Rob Herring
2021-08-19 18:42 ` [PATCH 3/5] arm: dts: vexpress: Drop unused properties from motherboard node Rob Herring
2021-08-19 18:42   ` Rob Herring
2021-08-19 18:42 ` [PATCH 4/5] arm: dts: vexpress-v2p-ca9: Fix the SMB unit-address Rob Herring
2021-08-19 18:42   ` Rob Herring
2021-08-19 18:42 ` [PATCH 5/5] arm: dts: vexpress: Fix addressing issues with 'motherboard-bus' nodes Rob Herring
2021-08-19 18:42   ` Rob Herring
2021-08-19 23:25 ` Linus Walleij [this message]
2021-08-19 23:25   ` [PATCH 0/5] Arm VExpress/Juno motherboard bus clean-ups Linus Walleij
2021-09-13 17:21 ` Sudeep Holla
2021-09-13 17:21   ` Sudeep Holla
2021-09-16  9:03 ` Sudeep Holla
2021-09-16  9:03   ` Sudeep Holla

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='CACRpkdavBq5vfvVQMJm-R32VP-FEO6j6L5pUGGCWEFSiN=tUDw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=andre.przywara@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=sudeep.holla@arm.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.