From: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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 v3 ath-current 2/2] dt-bindings: net: wireless: ath11k-pci: deprecate 'firmware-name' property
Date: Tue, 20 Jan 2026 09:31:15 +0800 [thread overview]
Message-ID: <61c8787d-ddfa-4cf8-b3fa-a85cc1526680@oss.qualcomm.com> (raw)
In-Reply-To: <2bf8dfc9-148a-4914-86a9-ebbb871a6887@kernel.org>
On 1/19/2026 10:48 PM, Krzysztof Kozlowski wrote:
> On 19/01/2026 15:02, 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.
>>
>> Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
>
>
> Is this the same patch as the one which received review/tag?
>
> Best regards,
> Krzysztof
Do you mean adding back the tag
‘Acked-by: Rob Herring (Arm) <robh@kernel.org>’ because the patch had no
changes when that review/tag was given?
prev parent reply other threads:[~2026-01-20 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 14:02 [PATCH v3 ath-current 0/2] wifi: ath11k: add usecase firmware handling based on device compatible Miaoqing Pan
2026-01-19 14:02 ` [PATCH v3 ath-current 1/2] " Miaoqing Pan
2026-01-19 15:56 ` Jonas Gorski
2026-01-20 1:31 ` Miaoqing Pan
2026-01-19 14:02 ` [PATCH v3 ath-current 2/2] dt-bindings: net: wireless: ath11k-pci: deprecate 'firmware-name' property Miaoqing Pan
2026-01-19 14:48 ` Krzysztof Kozlowski
2026-01-20 1:31 ` Miaoqing Pan [this message]
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=61c8787d-ddfa-4cf8-b3fa-a85cc1526680@oss.qualcomm.com \
--to=miaoqing.pan@oss.qualcomm.com \
--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=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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