[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20221205201720.68199051@kernel.org>
Date: Mon, 5 Dec 2022 20:17:20 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Luiz Augusto von Dentz <luiz.dentz@...il.com>
Cc: David Miller <davem@...emloft.net>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>
Subject: Re: pull-request: bluetooth 2022-12-02
Sorry for the delay, looks like the list ate your email :S
On Fri, 2 Dec 2022 23:49:18 -0800 Luiz Augusto von Dentz wrote:
> > On Fri, 2 Dec 2022 13:37:26 -0800 Luiz Augusto von Dentz wrote:
> > > bluetooth pull request for net:
> > >
> > > - Fix regressions with CSR controller clones
> > > - Fix support for Read Local Supported Codecs V2
> > > - Fix overflow on L2CAP code
> > > - Fix missing hci_dev_put on ISO and L2CAP code
> >
> > Two new sparse warnings in btusb.c here, please follow up to fix those.
>
> Do you have the logs somewhere?
Yes, but shouldn't matter, the output is actually quite messy.
I recommend running:
make W=1 C=1 path/to/file.o
and you'll see all the warnings.
> Or even better if you share the script you use to detect new sparse
> warning we can perhaps integrate in our ci.
Yes, yes, all our script are here:
https://github.com/kuba-moo/nipa/tree/master/tests
Build one is here:
https://github.com/kuba-moo/nipa/blob/master/tests/patch/build_allmodconfig_warn/build_allmodconfig.sh
It's relatively okay at catching build issues. But the output is messy,
as I said :(
Powered by blists - more mailing lists