From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Siddharth Vadapalli <s-vadapalli@ti.com>,
lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
bhelgaas@google.com, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, srk@ti.com
Subject: Re: [RFC PATCH] dt-bindings: PCI: ti,j721e-pci-host: Add device-id for TI's J784S4 SoC
Date: Mon, 8 Jan 2024 12:21:04 +0100 [thread overview]
Message-ID: <7d3439c2-35e3-4318-aa99-af9b7c8ed53b@linaro.org> (raw)
In-Reply-To: <bc3a0fb0-6268-476a-a13a-2d538704f61d@ti.com>
On 08/01/2024 11:20, Siddharth Vadapalli wrote:
> Hello Krzysztof,
>
> On 08/01/24 12:39, Krzysztof Kozlowski wrote:
>> On 08/01/2024 06:07, Siddharth Vadapalli wrote:
>>> Add the device-id of 0xb012 for the PCIe controller on the J784S4 SoC as
>>> described in the CTRL_MMR_PCI_DEVICE_ID register's PCI_DEVICE_ID_DEVICE_ID
>>> field. The Register descriptions and the Technical Reference Manual for
>>> J784S4 SoC can be found at: https://www.ti.com/lit/zip/spruj52
>>>
>>> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
>>> ---
>>>
>>> This patch is based on linux-next tagged next-20240105.
>>
>> Why is this patch incomplete? What is missing here? What are you asking
>> about as RFC?
>
> Since the merge window is closed, I was hoping to get the patch reviewed in
> order to get any "Reviewed-by" tags if possible. That way, I will be able to
> post it again as v1 along with the tags when the merge window opens. For that
This is v1, so that would be v2.
> reason, I have marked it as an RFC patch. Is there an alternative to this "RFC
> patch" method that I have followed? Please let me know.
Then how does it differ from posting without RFC? Sorry, RFC is
incomplete work. Often ignored during review.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-08 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 5:07 [RFC PATCH] dt-bindings: PCI: ti,j721e-pci-host: Add device-id for TI's J784S4 SoC Siddharth Vadapalli
2024-01-08 7:09 ` Krzysztof Kozlowski
2024-01-08 10:20 ` Siddharth Vadapalli
2024-01-08 11:21 ` Krzysztof Kozlowski [this message]
2024-01-08 11:34 ` Siddharth Vadapalli
2024-01-08 12:26 ` Krzysztof Kozlowski
2024-01-09 4:08 ` Siddharth Vadapalli
2024-01-13 1:45 ` Rob Herring
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=7d3439c2-35e3-4318-aa99-af9b7c8ed53b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@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).