From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rosen Penev <rosenp@gmail.com>,
linux-wireless@vger.kernel.org
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
nbd@nbd.name, "Johannes Berg" <johannes@sipsolutions.net>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:MIPS" <linux-mips@vger.kernel.org>
Subject: Re: [PATCHv5 0/5] wifi: ath9k: add ahb OF support
Date: Fri, 20 Jun 2025 08:27:30 -0700 [thread overview]
Message-ID: <4a3ad8a6-90a9-45c5-bbdf-7b91d3c18e51@oss.qualcomm.com> (raw)
In-Reply-To: <ddc48fa7-3fca-46a3-9224-11c0c3fce4a4@kernel.org>
On 6/19/2025 10:39 PM, Krzysztof Kozlowski wrote:
> On 20/06/2025 07:32, Krzysztof Kozlowski wrote:
>> On 20/06/2025 02:33, Jeff Johnson wrote:
>>> On 6/8/2025 8:08 PM, Rosen Penev wrote:
>>>> First two commits are small cleanups to make the changes of the third
>>>> simpler. The fourth actually adds dts definitions to use ahb.
>>>>
>>>> v2: Add documentation, use kernel_ulong_t, and of_device_get_match_data
>>>> v3: Use qcom prefix and wifi suffix as in other ath drivers.
>>>> v4: fix up dts example in Documentation
>>>> v5: move back to using qca prefix. It makes no sense to diverge between
>>>> all the other drivers for MIPS based qualcomm devices. qcom as a prefix
>>>> is used for Quallcomm's ARM(64) stuff.
>>>>
>>>> Rosen Penev (5):
>>>> wifi: ath9k: ahb: reorder declarations
>>>> wifi: ath9k: ahb: reorder includes
>>>> wifi: ath9k: ahb: replace id_table with of
>>>> dt-bindings: net: wireless: ath9k: add OF bindings
>>>> mips: dts: qca: add wmac support
>>>>
>>>> .../bindings/net/wireless/qca,ath9k.yaml | 23 ++++++-
>>>> arch/mips/boot/dts/qca/ar9132.dtsi | 9 +++
>>>> .../boot/dts/qca/ar9132_tl_wr1043nd_v1.dts | 4 ++
>>>> arch/mips/boot/dts/qca/ar9331.dtsi | 9 +++
>>>> arch/mips/boot/dts/qca/ar9331_dpt_module.dts | 4 ++
>>>> .../mips/boot/dts/qca/ar9331_dragino_ms14.dts | 4 ++
>>>> arch/mips/boot/dts/qca/ar9331_omega.dts | 4 ++
>>>> .../qca/ar9331_openembed_som9331_board.dts | 4 ++
>>>> arch/mips/boot/dts/qca/ar9331_tl_mr3020.dts | 4 ++
>>>> drivers/net/wireless/ath/ath9k/ahb.c | 60 +++++++------------
>>>> 10 files changed, 84 insertions(+), 41 deletions(-)
>>>>
>>>
>>> DT team, should I take this series through my tree?
>>> Toke, Ack?
>> No, of course not. The same as you asked some time ago: DTS never, NEVER
>> goes via driver subsystem tree.
>>
>
> Heh, you do not have any subsystem maintainers acks or reviews on DTS,
> so this should not be considered. It's like me taking wireless patches
> without your acks.
That is why I was looking for clarification.
All the DT stuff had your R-B and hence why I asked Toke for his Ack.
Will DT team take the entire series (I'm ok with that)?
Or just the DTS and I should take the rest?
/jeff
next prev parent reply other threads:[~2025-06-20 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 3:08 [PATCHv5 0/5] wifi: ath9k: add ahb OF support Rosen Penev
2025-06-09 3:08 ` [PATCHv5 1/5] wifi: ath9k: ahb: reorder declarations Rosen Penev
2025-06-09 3:08 ` [PATCHv5 2/5] wifi: ath9k: ahb: reorder includes Rosen Penev
2025-06-09 3:08 ` [PATCHv5 3/5] dt-bindings: net: wireless: ath9k: add WIFI bindings Rosen Penev
2025-06-09 3:08 ` [PATCHv5 4/5] wifi: ath9k: ahb: replace id_table with of Rosen Penev
2025-06-09 3:08 ` [PATCHv5 5/5] mips: dts: qca: add wmac support Rosen Penev
2025-07-02 12:28 ` Thomas Bogendoerfer
2025-06-20 0:33 ` [PATCHv5 0/5] wifi: ath9k: add ahb OF support Jeff Johnson
2025-06-20 5:32 ` Krzysztof Kozlowski
2025-06-20 5:39 ` Krzysztof Kozlowski
2025-06-20 15:27 ` Jeff Johnson [this message]
2025-06-20 15:45 ` Krzysztof Kozlowski
2025-06-20 8:50 ` Toke Høiland-Jørgensen
2025-06-26 23:15 ` (subset) " 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=4a3ad8a6-90a9-45c5-bbdf-7b91d3c18e51@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--cc=toke@toke.dk \
--cc=tsbogend@alpha.franken.de \
/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