public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	linux-renesas-soc@vger.kernel.org,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Marek Vasut" <marek.vasut+renesas@gmail.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Masami Hiramatsu" <mhiramat@kernel.org>,
	"Binghui Wang" <wangbinghui@hisilicon.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
	linux-arm-kernel@lists.infradead.org,
	"Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>,
	"Xiaowei Song" <songxiaowei@hisilicon.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: PCI: socionext,uniphier-pcie-ep: add top-level constraints
Date: Mon, 19 Aug 2024 11:14:45 -0600	[thread overview]
Message-ID: <172408768452.1698595.1459135684597826789.robh@kernel.org> (raw)
In-Reply-To: <20240818172843.121787-3-krzysztof.kozlowski@linaro.org>


On Sun, 18 Aug 2024 19:28:43 +0200, Krzysztof Kozlowski wrote:
> Properties with variable number of items per each device are expected to
> have widest constraints in top-level "properties:" block and further
> customized (narrowed) in "if:then:".  Add missing top-level constraints
> for clock-names and reset-names.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>  .../bindings/pci/socionext,uniphier-pcie-ep.yaml          | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>



  reply	other threads:[~2024-08-19 17:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18 17:28 [PATCH 1/3] dt-bindings: PCI: hisilicon,kirin-pcie: add top-level constraints Krzysztof Kozlowski
2024-08-18 17:28 ` [PATCH 2/3] dt-bindings: PCI: renesas,pci-rcar-gen2: " Krzysztof Kozlowski
2024-08-19 17:14   ` Rob Herring (Arm)
2024-08-18 17:28 ` [PATCH 3/3] dt-bindings: PCI: socionext,uniphier-pcie-ep: " Krzysztof Kozlowski
2024-08-19 17:14   ` Rob Herring (Arm) [this message]
2024-08-21 10:31   ` Kunihiko Hayashi
2024-08-19 17:14 ` [PATCH 1/3] dt-bindings: PCI: hisilicon,kirin-pcie: " Rob Herring (Arm)
2024-09-04 14:37 ` Krzysztof Wilczyński

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=172408768452.1698595.1459135684597826789.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=hayashi.kunihiko@socionext.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=mhiramat@kernel.org \
    --cc=songxiaowei@hisilicon.com \
    --cc=wangbinghui@hisilicon.com \
    --cc=yoshihiro.shimoda.uh@renesas.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