Re: pull-request: ath-next-20260721

On Tue, 2026-07-21 at 16:46 -0700, Jeff Johnson wrote:
>=20
> ----------------------------------------------------------------
>=20
> NOTE TO UPSTREAM MAINTAINERS
> This PR includes the merge of an immutable branch from the qcom tree
> https://lore.kernel.org/all/178362521364.2422497.1305957434056184382.b4-t=
[email protected]/

That's annoying, it added a kernel-doc warning that now shows up on our
output... I guess we need to ignore that.

> New warnings added:
> Warning: drivers/firmware/qcom/qcom_scm.c:1055 No description found for r=
eturn value of 'qcom_scm_is_pas_available'
> Warning: drivers/firmware/qcom/qcom_scm.c:1055 No description found for r=
eturn value of 'qcom_scm_is_pas_available'
> Per-file breakdown:
>      2 drivers/firmware/qcom/qcom_scm.c

I also get two fixes tag reports:

> Commit: b127f79a4933 ("wifi: ath12k: Correctly copy the hint BSSID in WMI=
 scan request")
> 	Fixes tag: Fixes: f40abb4788a2 ("ath12k: New driver for Qualcomm 11be hw=
 family")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> Commit: fde37c064641 ("wifi: ath12k: Set IEEE80211_OFFLOAD_ENCAP_4ADDR af=
ter tx_encap_type vdev param")
> 	Fixes tag: Fixes: 729cad3c3c9e ("wifi: ath12k: Add 4-address mode suppor=
t for eth offload")
> 	Has these problem(s):
> 		- empty lines surround the Fixes tag

Note that the first of those ... the commit exists, but not in the right
tree. It's in some ath12k-bringup-start tag in your tree, but not in
mainline, got a different sha1 there. So checking locally is confusing.

johannes