From: Kalle Valo <kvalo@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH net-next v2] dt-bindings: net: ath11k: document the inputs of the ath11k on WCN6855
Date: Thu, 19 Sep 2024 10:48:41 +0300 [thread overview]
Message-ID: <87msk49j8m.fsf@kernel.org> (raw)
In-Reply-To: <83c562e9-2add-4086-86e7-6e956d2ee70f@kernel.org> (Krzysztof Kozlowski's message of "Thu, 19 Sep 2024 08:55:36 +0200")
Krzysztof Kozlowski <krzk@kernel.org> writes:
> On 14/08/2024 10:23, Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>>
>> Describe the inputs from the PMU of the ath11k module on WCN6855.
>>
>> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>> ---
>> v1 -> v2:
>> - update the example
>
> I don't understand why this patch is no being picked up. The code
> correct represents the piece of hardware. The supplies should be
> required, because this one particular device - the one described in this
> binding - cannot work without them.
I have already explained the situation. With supplies changed to
optional I'm happy take the patch.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-09-19 7:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 8:23 [PATCH net-next v2] dt-bindings: net: ath11k: document the inputs of the ath11k on WCN6855 Bartosz Golaszewski
2024-08-14 16:25 ` Conor Dooley
2024-08-16 8:26 ` Kalle Valo
2024-08-16 9:10 ` Bartosz Golaszewski
2024-09-02 8:34 ` Bartosz Golaszewski
2024-09-05 15:47 ` Kalle Valo
2024-09-05 18:19 ` Bartosz Golaszewski
2024-09-05 18:28 ` Kalle Valo
2024-09-05 21:27 ` Krzysztof Kozlowski
2024-09-06 7:44 ` Bartosz Golaszewski
2024-09-06 18:38 ` Jeff Johnson
2024-09-09 8:19 ` Bartosz Golaszewski
2024-09-09 8:39 ` Bartosz Golaszewski
2024-09-19 6:55 ` Krzysztof Kozlowski
2024-09-19 7:48 ` Kalle Valo [this message]
2024-09-19 8:59 ` Bartosz Golaszewski
2024-09-20 6:22 ` Kalle Valo
2024-09-20 7:58 ` Bartosz Golaszewski
2024-09-19 10:00 ` Krzysztof Kozlowski
2024-09-20 6:45 ` Kalle Valo
2024-09-20 8:22 ` Bartosz Golaszewski
2024-09-20 21:02 ` Jeff Johnson
2024-09-21 4:56 ` Bartosz Golaszewski
2024-09-24 8:06 ` Krzysztof Kozlowski
2024-09-24 16:46 ` Jeff Johnson
2024-09-24 17:07 ` Bartosz Golaszewski
2024-09-24 8:04 ` Krzysztof Kozlowski
2024-09-25 5:58 ` Kalle Valo
2024-09-25 7:10 ` Krzysztof Kozlowski
2024-09-28 9:22 ` Kalle Valo
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=87msk49j8m.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jjohnson@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.