From: Krzysztof Kozlowski <krzk@kernel.org>
To: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>,
jjohnson@kernel.org, johannes@sipsolutions.net, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 ath-current 2/2] dt-bindings: net: wireless: ath11k-pci: remove obsolete firmware-name property
Date: Tue, 13 Jan 2026 08:28:43 +0100 [thread overview]
Message-ID: <fa997674-402a-41cf-9334-f7fc89ae5ebc@kernel.org> (raw)
In-Reply-To: <20251214025230.716387-3-miaoqing.pan@oss.qualcomm.com>
On 14/12/2025 03:52, Miaoqing Pan wrote:
> The firmware-name property was introduced to allow end-users and
> integrators to select usecase specific firmware for the WCN6855.
> However, specifying firmware for an M.2 WLAN module in the Device
> Tree is not appropriate. Instead, this functionality will be handled
> within the ath11k driver.
>
> The driver has removed all support for firmware-name, and no upstream
> Device Tree files reference this property. Therefore, this patch
> removes the property from the binding and marks it as obsolete.
No, it does not mark it obsolete. Point me to the place.
>
> This is a DT ABI-breaking change, but safe since there are no in-tree
> users.
It's not safe. What about my board using this WiFi? Or Mr. foo's board?
Still NAK, you did not improve it.
>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
And that's a fake tag.
Rob never acked such patch! Adding tags for something completely
different is not acceptable.
Nacked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
> ---
> .../devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml
> index e34d42a30192..653b319fee88 100644
> --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml
> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml
> @@ -35,12 +35,6 @@ properties:
> string to uniquely identify variant of the calibration data for designs
> with colliding bus and device ids
>
> - firmware-name:
> - maxItems: 1
> - description:
> - If present, a board or platform specific string used to lookup
> - usecase-specific firmware files for the device.
> -
> vddrfacmn-supply:
> description: VDD_RFA_CMN supply regulator handle
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-13 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 2:52 [PATCH v2 ath-current 0/2]] wifi: ath11k: add usecase firmware handling based on device compatible Miaoqing Pan
2025-12-14 2:52 ` [PATCH v2 ath-current 1/2] " Miaoqing Pan
2026-01-13 7:30 ` Krzysztof Kozlowski
2025-12-14 2:52 ` [PATCH v2 ath-current 2/2] dt-bindings: net: wireless: ath11k-pci: remove obsolete firmware-name property Miaoqing Pan
2026-01-13 7:28 ` Krzysztof Kozlowski [this message]
2026-01-19 1:34 ` Miaoqing Pan
2026-01-19 7:08 ` Krzysztof Kozlowski
2026-01-19 13:17 ` Miaoqing Pan
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=fa997674-402a-41cf-9334-f7fc89ae5ebc@kernel.org \
--to=krzk@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miaoqing.pan@oss.qualcomm.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