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,
jonas.gorski@gmail.com
Subject: Re: [PATCH v4 ath-current 2/2] dt-bindings: net: wireless: ath11k-pci: deprecate 'firmware-name' property
Date: Wed, 28 Jan 2026 09:00:47 +0100 [thread overview]
Message-ID: <45a07659-4eed-418c-837f-b3a96d519768@kernel.org> (raw)
In-Reply-To: <20260121095055.3683957-3-miaoqing.pan@oss.qualcomm.com>
On 21/01/2026 10:50, Miaoqing Pan wrote:
> The firmware-name property was originally introduced to allow end-users
> and integrators to select use-case-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. Therefore, the firmware-name property is now
> deprecated.
>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
> ---
> .../devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-28 8:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 9:50 [PATCH v4 ath-current 0/2] wifi: ath11k: add usecase firmware handling based on device compatible Miaoqing Pan
2026-01-21 9:50 ` [PATCH v4 ath-current 1/2] " Miaoqing Pan
2026-01-28 15:42 ` Vasanthakumar Thiagarajan
2026-01-29 2:10 ` Baochen Qiang
2026-01-21 9:50 ` [PATCH v4 ath-current 2/2] dt-bindings: net: wireless: ath11k-pci: deprecate 'firmware-name' property Miaoqing Pan
2026-01-28 8:00 ` Krzysztof Kozlowski [this message]
2026-01-27 17:31 ` [PATCH v4 ath-current 0/2] wifi: ath11k: add usecase firmware handling based on device compatible Jeff Johnson
2026-01-28 8:01 ` Krzysztof Kozlowski
2026-01-28 8:06 ` Miaoqing Pan
2026-01-28 15:30 ` Jeff Johnson
2026-01-30 15:15 ` Jeff Johnson
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=45a07659-4eed-418c-837f-b3a96d519768@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=jonas.gorski@gmail.com \
--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