From: Jakub Kicinski <kuba@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: David Miller <davem@davemloft.net>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: Re: pull-request: bluetooth 2022-12-02
Date: Mon, 5 Dec 2022 20:17:20 -0800 [thread overview]
Message-ID: <20221205201720.68199051@kernel.org> (raw)
In-Reply-To: <CABBYNZKhyTcAJkBt5pg4ymU530h5wie3OACU5HVX4dR37=1ZAw@mail.gmail.com>
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 :(
next prev parent reply other threads:[~2022-12-06 4:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 21:37 pull-request: bluetooth 2022-12-02 Luiz Augusto von Dentz
2022-12-03 4:32 ` Jakub Kicinski
[not found] ` <CABBYNZKhyTcAJkBt5pg4ymU530h5wie3OACU5HVX4dR37=1ZAw@mail.gmail.com>
2022-12-06 4:17 ` Jakub Kicinski [this message]
2022-12-03 4:40 ` patchwork-bot+netdevbpf
2022-12-12 22:32 ` patchwork-bot+bluetooth
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=20221205201720.68199051@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).