From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>, ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: net: wireless: describe the ath12k AHB module
Date: Tue, 28 Jan 2025 11:21:04 +0100 [thread overview]
Message-ID: <112fe636-1328-49f0-8f0a-395764e118c7@kernel.org> (raw)
In-Reply-To: <1bd2dca3-1fa0-424d-95e8-cdb887f1d9e2@quicinc.com>
On 28/01/2025 10:29, Raj Kumar Bhagat wrote:
> On 1/28/2025 2:47 PM, Krzysztof Kozlowski wrote:
>> On 28/01/2025 10:10, Raj Kumar Bhagat wrote:
>>> Add device-tree bindings for the ATH12K module found in the IPQ5332
>>> device.
>>>
>>> Signed-off-by: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>
>>> ---
>>> .../net/wireless/qcom,ath12k-ahb.yaml | 317 ++++++++++++++++++
>>> 1 file changed, 317 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/net/wireless/qcom,ath12k-ahb.yaml
>>
>> It was v4, now v1? So entire previous discussion and feedback is
>> missing? Go to previous series and implement entire feedback. Then use
>> proper versioning, proper changelog and make it obvious/understandable
>> to us, instead of sending v1 after v4 in entirely separate thread.
>>
>
> I was asked to send DTS as a separate series, this is a new series for
> DTS hence stated with v1.
But we do not talk about DTS here, but bindings.
> To address the undocumented ABIs we have changes in dt-binding and hence
That's v1 so how it could have changes in the first place? Unless this
is v5?
> corresponding changes in driver as well. Let me know If we could send the
> complete series as v5.
>
>> I also do not understand why this is sent to arm soc. That's wireless patch.
>>
>
> All the email list are as per - './scripts/get_maintainer.pl'
I am asking why this patch is part of the arm soc patchset. This is
networking/wireless patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-28 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 9:10 [PATCH 0/2] dt-bindings: net: wireless: add wifi node for IPQ5332 Raj Kumar Bhagat
2025-01-28 9:10 ` [PATCH 1/2] dt-bindings: net: wireless: describe the ath12k AHB module Raj Kumar Bhagat
2025-01-28 9:17 ` Krzysztof Kozlowski
2025-01-28 9:29 ` Raj Kumar Bhagat
2025-01-28 10:21 ` Krzysztof Kozlowski [this message]
2025-01-28 17:34 ` Raj Kumar Bhagat
2025-01-28 9:10 ` [PATCH 2/2] arm64: dts: qcom: add wifi node for IPQ5332 based RDP441 Raj Kumar Bhagat
2025-01-28 9:22 ` Krzysztof Kozlowski
2025-01-28 9:41 ` Raj Kumar Bhagat
2025-01-28 10:24 ` Krzysztof Kozlowski
2025-01-28 16:46 ` Raj Kumar Bhagat
2025-01-28 11:32 ` Konrad Dybcio
2025-01-28 17:00 ` Raj Kumar Bhagat
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=112fe636-1328-49f0-8f0a-395764e118c7@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjohnson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rajkbhag@quicinc.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