From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Achal Verma <a-verma1@ti.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Krzysztof Wilczy_ski <kw@linux.com>,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Dhananjay Vilasrao Kangude <dkangude@cadence.com>,
Anindita Das <dasa@cadence.com>, Yuan Zhao <yuanzhao@cadence.com>,
Milind Parab <mparab@cadence.com>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v11 1/5] dt-bindings: PCI: ti,j721e-pci-*: add checks for num-lanes
Date: Sun, 19 Mar 2023 12:23:41 +0100 [thread overview]
Message-ID: <64d0dffd-a5ce-4667-9d56-1c109ec73866@linaro.org> (raw)
In-Reply-To: <20230317075120.506267-2-a-verma1@ti.com>
On 17/03/2023 08:51, 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
next prev parent reply other threads:[~2023-03-19 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 7:51 [PATCH v11 0/5] PCI: add 4x lane support for pci-j721e controllers Achal Verma
2023-03-17 7:51 ` [PATCH v11 1/5] dt-bindings: PCI: ti,j721e-pci-*: add checks for num-lanes Achal Verma
2023-03-19 11:23 ` Krzysztof Kozlowski [this message]
2023-03-17 7:51 ` [PATCH v11 2/5] PCI: j721e: Add per platform maximum lane settings Achal Verma
2023-03-17 7:51 ` [PATCH v11 3/5] PCI: j721e: Add PCIe 4x lane selection support Achal Verma
2023-03-17 7:51 ` [PATCH v11 4/5] dt-bindings: PCI: ti,j721e-pci-*: add j784s4-pci-* compatible strings Achal Verma
2023-03-17 7:51 ` [PATCH v11 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=64d0dffd-a5ce-4667-9d56-1c109ec73866@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=a-verma1@ti.com \
--cc=bhelgaas@google.com \
--cc=dasa@cadence.com \
--cc=devicetree@vger.kernel.org \
--cc=dkangude@cadence.com \
--cc=krzysztof.kozlowski+dt@linaro.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=mparab@cadence.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=yuanzhao@cadence.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).