Re: [PATCH v10 1/5] dt-bindings: net: wireless: brcm4329-fmac: add pci14e4,449d

[Arend van Spriel <arend.vanspriel@broadcom.com>]

On 8/14/2024 12:39 PM, Krzysztof Kozlowski wrote:
> On 14/08/2024 12:08, Arend van Spriel wrote:
>> On 8/14/2024 10:53 AM, Krzysztof Kozlowski wrote:
>>> On 13/08/2024 19:04, Arend Van Spriel wrote:
>>>> On August 13, 2024 10:20:24 AM Jacobe Zang <jacobe.zang@wesion.com> wrote:
>>>>
>>>>> It's the device id used by AP6275P which is the Wi-Fi module
>>>>> used by Rockchip's RK3588 evaluation board and also used in
>>>>> some other RK3588 boards.
>>>>
>>>> Hi Kalle,
>>>>
>>>> There probably will be a v11, but wanted to know how this series will be
>>>> handled as it involves device tree bindings, arm arch device tree spec, and
>>>> brcmfmac driver code. Can it all go through wireless-next?
>>>
>>> No, DTS must not go via wireless-next. Please split it from the series
>>> and provide lore link in changelog for bindings.
>>
>> Hi Krzysztof,
>>
>> Is it really important how the patches travel upstream to Linus. This
>> binding is specific to Broadcom wifi devices so there are no
>> dependencies(?). To clarify what you are asking I assume two separate
>> series:
>>
>> 1) DT binding + Khadas Edge2 DTS  -> devicetree@vger.kernel.org
>> 	reference to:
>> https://patch.msgid.link/20240813082007.2625841-1-jacobe.zang@wesion.com
>>
>> 2) brcmfmac driver changes	  -> linux-wireless@vger.kernel.org
> 
> No. I said only DTS is separate. This was always the rule, since forever.
> 
> Documentation/devicetree/bindings/submitting-patches.rst

I am going slightly mad (by Queen). That documents says:

   1) The Documentation/ and include/dt-bindings/ portion of the patch 
should
      be a separate patch.

and

   4) Submit the entire series to the devicetree mailinglist at

        devicetree@vger.kernel.org

Above I mentioned "series", not "patch". So 1) is a series of 3 patches 
(2 changes to the DT binding file and 1 patch for the Khadas Edge2 DTS. 
Is that correct?

Regards,
Arend