Re: pull-request: ath-next-20260721

On Wed, 2026-07-22 at 08:51 -0700, Jeff Johnson wrote:
> On 7/22/2026 7:08 AM, Johannes Berg wrote:
> > 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.=
[email protected]/
> >=20
> > That's annoying, it added a kernel-doc warning that now shows up on our
> > output... I guess we need to ignore that.
> >=20
> > > New warnings added:
> > > Warning: drivers/firmware/qcom/qcom_scm.c:1055 No description found f=
or return value of 'qcom_scm_is_pas_available'
> > > Warning: drivers/firmware/qcom/qcom_scm.c:1055 No description found f=
or return value of 'qcom_scm_is_pas_available'
> > > Per-file breakdown:
> > >      2 drivers/firmware/qcom/qcom_scm.c
>=20
> :(
>=20
> I run kernel-doc on the patches I process, but since I didn't directly pr=
ocess
> that series I didn't see it.

Yeah, no worries. Also they're outside our normal set of files, so I saw
them only because of the diff, not in my normal "check everything"
process. I'm not really bothered by it, just a heads-up.

> > Note that the first of those ... the commit exists, but not in the righ=
t
> > 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.
>=20
> Let me rewrite those and send another PR

Thanks!

johannes