From: pavi1729 <pavitra1729@gmail.com>
To: Jeff Haran <Jeff.Haran@citrix.com>
Cc: "kernelnewbies@kernelnewbies.org"
<kernelnewbies@kernelnewbies.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: Does the Community use Coverity ?
Date: Thu, 17 Dec 2015 15:34:19 +0530 [thread overview]
Message-ID: <CAMf7+Li74m2_nZru3kfwJZ5G9r7W69pwkarHbccs1xw-G8ZjnA@mail.gmail.com> (raw)
In-Reply-To: <4E5779AD88B2F040B8A7E83ECF544D1A64A4CF@SJCPEX01CL03.citrite.net>
Sanket, Jeff,
Thanks a ton, that was helpful.
Cheers,
Pavi
On Wed, Dec 16, 2015 at 12:32 AM, Jeff Haran <Jeff.Haran@citrix.com> wrote:
>>-----Original Message-----
>>From: kernelnewbies-bounces+jharan=bytemobile.com@kernelnewbies.org
>>[mailto:kernelnewbies-
>>bounces+jharan=bytemobile.com@kernelnewbies.org] On Behalf Of
>>pavi1729
>>Sent: Monday, December 14, 2015 11:03 PM
>>To: kernelnewbies@kernelnewbies.org; linux-fsdevel@vger.kernel.org; linux-
>>mmc@vger.kernel.org; linux-netdev@vger.kernel.org
>>Subject: Does the Community use Coverity ?
>>
>>Hi,
>> May I know if the community uses the Coverity tool and, if yes where can I
>>find a repo of Coverity scans of kernels and IGNORE LIST; cause there
>>obviously would be false positives.
>>
>>Cheers,
>>Pavi
>
> https://scan.coverity.com/
>
> Sign up for an account and join the Linux project.
>
> Jeff Haran
>
next prev parent reply other threads:[~2015-12-17 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 7:02 Does the Community use Coverity ? pavi1729
2015-12-15 8:15 ` Saket Sinha
2015-12-15 19:02 ` Jeff Haran
2015-12-17 10:04 ` pavi1729 [this message]
2015-12-21 18:22 ` Jeff Haran
2016-01-07 22:06 ` Ricardo Ribalda Delgado
2015-12-21 7:16 ` Ruben Safir
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=CAMf7+Li74m2_nZru3kfwJZ5G9r7W69pwkarHbccs1xw-G8ZjnA@mail.gmail.com \
--to=pavitra1729@gmail.com \
--cc=Jeff.Haran@citrix.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--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).