From: Krzysztof Kozlowski <krzk@kernel.org>
To: Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
Raj Kumar Bhagat <raj.bhagat@oss.qualcomm.com>,
Johannes Berg <johannes@sipsolutions.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ath12k@lists.infradead.org,
Saravanakumar Duraisamy <quic_saradura@quicinc.com>,
Sowmiya Sree Elavalagan <sowmiya.elavalagan@oss.qualcomm.com>
Subject: Re: [PATCH ath-next v4 0/6] wifi: ath12k: Enable IPQ5424 AHB WiFi device
Date: Sat, 4 Apr 2026 07:23:29 +0200 [thread overview]
Message-ID: <95face24-deaf-47c4-935d-0b48b5141371@kernel.org> (raw)
In-Reply-To: <5a606f7d-6665-4b0c-bbbe-32538b2315b6@oss.qualcomm.com>
On 03/04/2026 11:13, Baochen Qiang wrote:
>>
>> .../bindings/net/wireless/qcom,ipq5332-wifi.yaml | 1 +
>> drivers/net/wireless/ath/ath12k/ahb.c | 36 +++++----
>> drivers/net/wireless/ath/ath12k/ahb.h | 1 +
>> drivers/net/wireless/ath/ath12k/ce.h | 13 ++-
>> drivers/net/wireless/ath/ath12k/core.h | 1 +
>> drivers/net/wireless/ath/ath12k/wifi7/ahb.c | 8 ++
>> drivers/net/wireless/ath/ath12k/wifi7/hal.c | 7 ++
>> drivers/net/wireless/ath/ath12k/wifi7/hal.h | 3 +
>> .../net/wireless/ath/ath12k/wifi7/hal_qcn9274.c | 88 ++++++++++++++++++++
>> .../net/wireless/ath/ath12k/wifi7/hal_qcn9274.h | 1 +
>> drivers/net/wireless/ath/ath12k/wifi7/hw.c | 93 +++++++++++++++++++++-
>> 11 files changed, 231 insertions(+), 21 deletions(-)
>> ---
>> base-commit: 15551ababf6d4e857f2101366a0c3eaa86dd822c
>> change-id: 20260331-ath12k-ipq5424-cddb63a46a97
>>
>
> only nit in patch 2/6, so for patches 2-6/6:
>
> Reviewed-by: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
It does not work like this. Replying to cover letter causes that all
patches will get it. Provide detailed review and response to each email
in such case.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-04-04 5:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 3:53 [PATCH ath-next v4 0/6] wifi: ath12k: Enable IPQ5424 AHB WiFi device Raj Kumar Bhagat
2026-04-02 3:53 ` [PATCH ath-next v4 1/6] dt-bindings: net: wireless: add ath12k wifi device IPQ5424 Raj Kumar Bhagat
2026-04-02 3:54 ` [PATCH ath-next v4 2/6] wifi: ath12k: Add ath12k_hw_params for IPQ5424 Raj Kumar Bhagat
2026-04-03 9:01 ` Baochen Qiang
2026-04-02 3:54 ` [PATCH ath-next v4 3/6] wifi: ath12k: add ath12k_hw_version_map entry " Raj Kumar Bhagat
2026-04-02 3:54 ` [PATCH ath-next v4 4/6] wifi: ath12k: add ath12k_hw_regs " Raj Kumar Bhagat
2026-04-02 3:54 ` [PATCH ath-next v4 5/6] wifi: ath12k: Add CE remap hardware parameters " Raj Kumar Bhagat
2026-04-02 3:54 ` [PATCH ath-next v4 6/6] wifi: ath12k: Enable IPQ5424 WiFi device support Raj Kumar Bhagat
2026-04-03 9:13 ` [PATCH ath-next v4 0/6] wifi: ath12k: Enable IPQ5424 AHB WiFi device Baochen Qiang
2026-04-04 5:23 ` Krzysztof Kozlowski [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=95face24-deaf-47c4-935d-0b48b5141371@kernel.org \
--to=krzk@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--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=quic_saradura@quicinc.com \
--cc=raj.bhagat@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sowmiya.elavalagan@oss.qualcomm.com \
/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