public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kalle Valo <kvalo@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, ath12k@lists.infradead.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v9 1/2] dt-bindings: net: wireless: qcom,ath11k: describe the ath11k on QCA6390
Date: Mon, 24 Jun 2024 11:26:50 +0200	[thread overview]
Message-ID: <c4e17f42-2ad2-4979-983b-5f1e2a0b1ed8@kernel.org> (raw)
In-Reply-To: <871q4mk8fw.fsf@kernel.org>

On 24/06/2024 11:15, Kalle Valo wrote:
> Krzysztof Kozlowski <krzk@kernel.org> writes:
> 
>> On 17/06/2024 13:09, Kalle Valo wrote:
>>> Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>>>
>>>> Add a PCI compatible for the ATH11K module on QCA6390 and describe the
>>>> power inputs from the PMU that it consumes.
>>>>
>>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>>>> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
>>>
>>> 2 patches applied to ath-next branch of ath.git, thanks.
>>
>> Hi Kalle,
>>
>> Are you sure your tree is properly fed to linux-next? I cannot find
>> these patches in linux-next and above repo is not listed in Next/Trees.
> 
> ath.git is not included in linux-next builds. To my knowledge wireless
> and wireless-next trees are the only trees from the wireless subsystem
> which are included, all driver trees are not. But Jeff and I are talking
> about including ath.git to linux-next.

Thanks for confirming. There is not much to "talk". Just send one email.
There is no single issue stopping you from being in linux-next. The only
work/caveat is when wireless-next cherry-picks your patches instead of
git pull, but even then you can arrange with Stephen to opt-out from
emails about duplicated commits.

Of course this is not specific to Ath - as you said - all wireless
sub-trees should be fixed. It's really odd that these are not in linux-next.

Best regards,
Krzysztof


  reply	other threads:[~2024-06-24  9:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 12:21 [PATCH v9 0/2] dt-bindings: describe the ath1X modules on QCom BT/WLAN chipsets Bartosz Golaszewski
2024-06-05 12:21 ` [PATCH v9 1/2] dt-bindings: net: wireless: qcom,ath11k: describe the ath11k on QCA6390 Bartosz Golaszewski
2024-06-06 13:30   ` Kalle Valo
2024-06-06 13:35     ` Bartosz Golaszewski
2024-06-06 14:01       ` Kalle Valo
2024-06-06 14:29         ` Bartosz Golaszewski
2024-06-06 16:16           ` Kalle Valo
2024-06-06 18:08             ` Bartosz Golaszewski
2024-06-07  6:40               ` Krzysztof Kozlowski
2024-06-11 20:05                 ` Bartosz Golaszewski
2024-06-12 12:49                   ` Kalle Valo
2024-06-12 12:52                     ` Bartosz Golaszewski
2024-06-14  7:18                       ` Bartosz Golaszewski
2024-06-17  9:09                         ` Kalle Valo
2024-06-12 12:42               ` Kalle Valo
2024-06-17 11:09   ` Kalle Valo
2024-06-24  7:00     ` Krzysztof Kozlowski
2024-06-24  9:15       ` Kalle Valo
2024-06-24  9:26         ` Krzysztof Kozlowski [this message]
2024-06-05 12:21 ` [PATCH v9 2/2] dt-bindings: net: wireless: describe the ath12k PCI module Bartosz Golaszewski
2024-06-06 13:34   ` Kalle Valo
2024-06-06 13:37     ` Bartosz Golaszewski
2024-06-06 13:35 ` [PATCH v9 0/2] dt-bindings: describe the ath1X modules on QCom BT/WLAN chipsets Kalle Valo
2024-06-06 18:19   ` 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=c4e17f42-2ad2-4979-983b-5f1e2a0b1ed8@kernel.org \
    --to=krzk@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=ath12k@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=krzysztof.kozlowski@linaro.org \
    --cc=kuba@kernel.org \
    --cc=kvalo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox