From: Bjorn Helgaas <helgaas@kernel.org>
To: Achal Verma <a-verma1@ti.com>
Cc: mranostay@ti.com, rogerq@kernel.org, lpieralisi@kernel.org,
robh@kernel.org, kw@linux.com, bhelgaas@google.com,
krzysztof.kozlowski@linaro.org, vigneshr@ti.com,
tjoseph@cadence.com, sergio.paracuellos@gmail.com,
pthombar@cadence.com, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 5/5] PCI: j721e: add j784s4 PCIe configuration
Date: Wed, 18 Jan 2023 10:56:44 -0600 [thread overview]
Message-ID: <20230118165644.GA225110@bhelgaas> (raw)
In-Reply-To: <20230118125936.3456716-6-a-verma1@ti.com>
If you repost for some other reason, fix the subject typo ("Add ..."
to match the others). Otherwise, Lorenzo may fix it up while
applying.
On Wed, Jan 18, 2023 at 06:29:36PM +0530, Achal Verma wrote:
> From: Matt Ranostay <mranostay@ti.com>
>
> Add PCIe configuration for j784s4 platform which has 4x lane support.
>
> Tested-by: Achal Verma <a-verma1@ti.com>
> Signed-off-by: Matt Ranostay <mranostay@ti.com>
> Reviewed-by: Roger Quadros <rogerq@kernel.org>
> Signed-off-by: Achal Verma <a-verma1@ti.com>
prev parent reply other threads:[~2023-01-18 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 12:59 [PATCH v8 0/5] PCI: add 4x lane support for pci-j721e controllers Achal Verma
2023-01-18 12:59 ` [PATCH v8 1/5] dt-bindings: PCI: ti,j721e-pci-*: add checks for num-lanes Achal Verma
2023-01-19 15:38 ` Krzysztof Kozlowski
2023-01-18 12:59 ` [PATCH v8 2/5] PCI: j721e: Add per platform maximum lane settings Achal Verma
2023-01-18 12:59 ` [PATCH v8 3/5] PCI: j721e: Add PCIe 4x lane selection support Achal Verma
2023-01-18 12:59 ` [PATCH v8 4/5] dt-bindings: PCI: ti,j721e-pci-*: add j784s4-pci-* compatible strings Achal Verma
2023-01-18 12:59 ` [PATCH v8 5/5] PCI: j721e: add j784s4 PCIe configuration Achal Verma
2023-01-18 16:56 ` Bjorn Helgaas [this message]
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=20230118165644.GA225110@bhelgaas \
--to=helgaas@kernel.org \
--cc=a-verma1@ti.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.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-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).