lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4c3d4437-4c24-4db3-855d-f2ba7d0c6f8a@kernel.org>
Date: Mon, 24 Jun 2024 09:00:56 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Kalle Valo <kvalo@...nel.org>, Bartosz Golaszewski <brgl@...ev.pl>
Cc: "David S . Miller" <davem@...emloft.net>,
 Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
 Paolo Abeni <pabeni@...hat.com>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Jeff Johnson <jjohnson@...nel.org>,
 linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
 devicetree@...r.kernel.org, ath11k@...ts.infradead.org,
 linux-kernel@...r.kernel.org, ath12k@...ts.infradead.org,
 Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v9 1/2] dt-bindings: net: wireless: qcom,ath11k: describe
 the ath11k on QCA6390

On 17/06/2024 13:09, Kalle Valo wrote:
> Bartosz Golaszewski <brgl@...ev.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@...aro.org>
>> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>> Signed-off-by: Kalle Valo <quic_kvalo@...cinc.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.

Every maintainer tree should (IMHO: *MUST*) be fed to linux-next.

You will also get LKP coverage for free, unless your tree is there due
to scanning korg.

Please look at slides here and implement at least linux-next (although I
also encourage to opt-in to transparency log and LKP):
https://lpc.events/event/17/contributions/1498/

Best regards,
Krzysztof


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ