From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ryder Lee <Ryder.Lee@mediatek.com>
Cc: "robh@kernel.org" <robh@kernel.org>,
"nbd@nbd.name" <nbd@nbd.name>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Allen Ye (葉芷勳)" <Allen.Ye@mediatek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] dt-bindings: net: wireless: mt76: clarify backoff limit format
Date: Wed, 11 Feb 2026 10:08:02 +0100 [thread overview]
Message-ID: <388e874d-d9ff-43f2-b010-ca7ac29aa065@kernel.org> (raw)
In-Reply-To: <0572bd6e56ca872e285729ccd4c2201517b66e18.camel@mediatek.com>
On 11/02/2026 09:59, Ryder Lee wrote:
> On Wed, 2026-02-11 at 09:41 +0100, Krzysztof Kozlowski wrote:
>> On 11/02/2026 09:33, Ryder Lee wrote:
>>>>>> Why this cannot be a schema?
>>>>>>
>>>>>>
>>>>> Well, actually, it's already a schema. This is just an expanded
>>>>
>>>> Where exactly?
>>>>
>>>
>>> How 1T1ss is used across different generations is what my example
>>> above
>>> was talking about.
>>
>> Where exactly it is already a schema? Please point me line encoding
>> this.
>>
>>
> line 243 paths-ru
> line 261 paths-ru-bf
I do not see there anything like you wrote here. You just list all of
them, no device constraints.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-11 9:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 18:08 [PATCH v3 1/2] wifi: mt76: fix backoff fields and max_power calculation Ryder Lee
2026-02-10 18:08 ` [PATCH v3 2/2] dt-bindings: net: wireless: mt76: clarify backoff limit format Ryder Lee
2026-02-10 18:12 ` Ryder Lee
2026-02-10 18:16 ` Ryder Lee
2026-02-11 6:31 ` Krzysztof Kozlowski
2026-02-11 8:13 ` Ryder Lee
2026-02-11 8:16 ` Krzysztof Kozlowski
2026-02-11 8:33 ` Ryder Lee
2026-02-11 8:41 ` Krzysztof Kozlowski
2026-02-11 8:59 ` Ryder Lee
2026-02-11 9:08 ` Krzysztof Kozlowski [this message]
2026-02-11 9:19 ` Ryder Lee
2026-02-11 9:35 ` Ryder Lee
2026-02-11 9:52 ` Chen-Yu Tsai
2026-02-11 16:26 ` Ryder Lee
2026-02-11 9:01 ` Chen-Yu Tsai
2026-02-11 9:07 ` Ryder Lee
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=388e874d-d9ff-43f2-b010-ca7ac29aa065@kernel.org \
--to=krzk@kernel.org \
--cc=Allen.Ye@mediatek.com \
--cc=Ryder.Lee@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.