From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] common/usb_storage.c: Clean up usb_storage_probe()
Date: Sun, 11 Oct 2015 08:24:43 -0400 [thread overview]
Message-ID: <20151011122443.GX3829@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmWWGCrkMprL4rTMhss3fEhHnhOaLZZMiCYLmDPZmh3-Lg@mail.gmail.com>
On Sun, Oct 11, 2015 at 08:05:11PM +0800, Bin Meng wrote:
> Hi Tom,
>
> On Sun, Oct 11, 2015 at 7:26 PM, Tom Rini <trini@konsulko.com> wrote:
> > We have the protocol and subclass variables which are used only in
> > disabled debug code. This code dates back to the initial git import and
> > seemingly dead code so remove it.
> >
> > This was detected by Coverity (CID 131117)
>
> Just out of curiosity, is this Coverity public available for the
> community to use?
We are (and technically we've had this since May 2014) a community
project. The ELC-E talk about using coverity reminded me to go give
things a spin and see what comes out. Right now I'm trying to figure
out the best way to get coverage for all of our different build targets
or if we may have to just go with building sandbox only for maximal
coverage (and make use of something like CONFIG_COMPILE_TEST_ONLY from
the kernel).
There is a way to make all defects publically viewable but I don't know
if that's a great idea or not (I don't see anything super duper worrying
but I also haven't really triaged everything) but anyone from the
community can sign up and join the project.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151011/c6320eb7/attachment.sig>
next prev parent reply other threads:[~2015-10-11 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 11:26 [U-Boot] [PATCH] common/usb_storage.c: Clean up usb_storage_probe() Tom Rini
2015-10-11 12:05 ` Bin Meng
2015-10-11 12:24 ` Tom Rini [this message]
2015-10-11 12:17 ` Marek Vasut
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=20151011122443.GX3829@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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