linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Achal Verma <a-verma1@ti.com>,
	mranostay@ti.com, rogerq@kernel.org, lpieralisi@kernel.org,
	robh@kernel.org, kw@linux.com, bhelgaas@google.com,
	vigneshr@ti.com, tjoseph@cadence.com,
	sergio.paracuellos@gmail.com, pthombar@cadence.com,
	linux-pci@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 1/5] dt-bindings: PCI: ti,j721e-pci-*: add checks for num-lanes
Date: Sun, 22 Jan 2023 15:30:02 +0100	[thread overview]
Message-ID: <a20028e6-3318-26ca-117a-26c87c292139@linaro.org> (raw)
In-Reply-To: <20230122122121.3552375-2-a-verma1@ti.com>

On 22/01/2023 13:21, Achal Verma wrote:
> From: Matt Ranostay <mranostay@ti.com>
> 
> Add num-lanes schema checks based on compatible string on available lanes
> for that platform.
> 
> Signed-off-by: Matt Ranostay <mranostay@ti.com>
> Signed-off-by: Achal Verma <a-verma1@ti.com>


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2023-01-22 14:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 12:21 [PATCH v9 0/5] PCI: add 4x lane support for pci-j721e controllers Achal Verma
2023-01-22 12:21 ` [PATCH v9 1/5] dt-bindings: PCI: ti,j721e-pci-*: add checks for num-lanes Achal Verma
2023-01-22 14:30   ` Krzysztof Kozlowski [this message]
2023-01-22 12:21 ` [PATCH v9 2/5] PCI: j721e: Add per platform maximum lane settings Achal Verma
2023-01-22 12:21 ` [PATCH v9 3/5] PCI: j721e: Add PCIe 4x lane selection support Achal Verma
2023-01-22 12:21 ` [PATCH v9 4/5] dt-bindings: PCI: ti,j721e-pci-*: add j784s4-pci-* compatible strings Achal Verma
2023-01-22 12:21 ` [PATCH v9 5/5] PCI: j721e: add j784s4 PCIe configuration Achal Verma

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=a20028e6-3318-26ca-117a-26c87c292139@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=a-verma1@ti.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mranostay@ti.com \
    --cc=pthombar@cadence.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=tjoseph@cadence.com \
    --cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).