linux-kernel - Re: [RFC PATCH] dt-bindings: PCI: ti,j721e-pci-host: Add device-id for TI's J784S4 SoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e4bd76d1-e5d9-4ff6-8917-db5784dea847@ti.com>
Date: Mon, 8 Jan 2024 17:04:14 +0530
From: Siddharth Vadapalli <s-vadapalli@...com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        <lpieralisi@...nel.org>, <kw@...ux.com>, <robh@...nel.org>,
        <bhelgaas@...gle.com>, <krzysztof.kozlowski+dt@...aro.org>,
        <conor+dt@...nel.org>
CC: <linux-pci@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        <srk@...com>, <s-vadapalli@...com>
Subject: Re: [RFC PATCH] dt-bindings: PCI: ti,j721e-pci-host: Add device-id
 for TI's J784S4 SoC



On 08/01/24 16:51, Krzysztof Kozlowski wrote:
> 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@...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.

I was under the impression that posting patches when the merge window is closed
will be met with a "post your patch later when the merge window is open"
response. That is why I chose the "RFC patch" path since RFCs can be posted anytime.

For the Networking Subsystem, it is documented that patches with new features
shouldn't be posted when the merge window is closed. I have mostly posted
patches for the Networking Subsystem and am not sure about the rules for the
device-tree bindings and PCI Subsystems. To be on the safe side I posted this
patch as an RFC patch.

Thank you for clarifying that it is alright to post patches even when merge
window is closed. Going forward I shall not post RFC patches unless it really
requires feedback and suggestions.

-- 
Regards,
Siddharth.