From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Jacobe Zang <jacobe.zang@wesion.com>,
robh@kernel.org, krzk+dt@kernel.org, heiko@sntech.de,
kvalo@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, conor+dt@kernel.org
Cc: efectn@protonmail.com, dsimic@manjaro.org, jagan@edgeble.ai,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
arend@broadcom.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, megi@xff.cz, duoming@zju.edu.cn,
bhelgaas@google.com, minipli@grsecurity.net,
brcm80211@lists.linux.dev, brcm80211-dev-list.pdl@broadcom.com,
nick@khadas.com,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v10 1/5] dt-bindings: net: wireless: brcm4329-fmac: add pci14e4,449d
Date: Wed, 14 Aug 2024 10:53:40 +0200 [thread overview]
Message-ID: <e7401e25-7802-4dc3-9535-226f32b52be1@kernel.org> (raw)
In-Reply-To: <1914cb2b1a8.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
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.
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-08-14 8:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 8:20 [PATCH v10 0/5] Add AP6275P wireless support Jacobe Zang
2024-08-13 8:20 ` [PATCH v10 1/5] dt-bindings: net: wireless: brcm4329-fmac: add pci14e4,449d Jacobe Zang
2024-08-13 17:04 ` Arend Van Spriel
2024-08-14 8:53 ` Krzysztof Kozlowski [this message]
2024-08-14 9:12 ` Jacobe Zang
2024-08-14 10:38 ` Krzysztof Kozlowski
2024-08-14 10:08 ` Arend van Spriel
2024-08-14 10:39 ` Krzysztof Kozlowski
2024-08-14 10:59 ` Arend van Spriel
2024-08-14 11:15 ` Krzysztof Kozlowski
2024-08-14 14:08 ` Krzysztof Kozlowski
2024-08-14 16:47 ` Arend Van Spriel
2024-08-15 9:38 ` Kalle Valo
2024-08-13 8:20 ` [PATCH v10 2/5] dt-bindings: net: wireless: brcm4329-fmac: add clock description for AP6275P Jacobe Zang
2024-08-13 8:20 ` [PATCH v10 3/5] arm64: dts: rockchip: Add AP6275P wireless support to Khadas Edge 2 Jacobe Zang
2024-08-13 8:20 ` [PATCH v10 4/5] wifi: brcmfmac: Add optional lpo clock enable support Jacobe Zang
2024-08-13 11:57 ` Arend van Spriel
2024-08-13 18:31 ` Arend van Spriel
2024-08-14 8:47 ` Alexey Charkov
2024-08-14 9:26 ` Jacobe Zang
2024-08-14 9:48 ` Alexey Charkov
2024-08-14 10:44 ` Arend van Spriel
2024-08-13 8:20 ` [PATCH v10 5/5] wifi: brcmfmac: add flag for random seed during firmware download Jacobe Zang
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=e7401e25-7802-4dc3-9535-226f32b52be1@kernel.org \
--to=krzk@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=bhelgaas@google.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=efectn@protonmail.com \
--cc=heiko@sntech.de \
--cc=jacobe.zang@wesion.com \
--cc=jagan@edgeble.ai \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=megi@xff.cz \
--cc=minipli@grsecurity.net \
--cc=netdev@vger.kernel.org \
--cc=nick@khadas.com \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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