All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: ben@coverity.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Coverity Open Source Defect Scan of Linux
Date: Tue, 14 Mar 2006 09:37:24 -0300	[thread overview]
Message-ID: <1142339844.4667.11.camel@praia> (raw)
In-Reply-To: <440BCA0F.50501@coverity.com>

Ben,

I'm the maintainer of V4L/DVB subsystem of the Linux Kernel
(http://linuxtv.org). I think your took may be usefull to our work.
Would you please give me an access to the tool?

Em Dom, 2006-03-05 às 21:35 -0800, Ben Chelf escreveu:
> Hello Linux Developers,
> 
>    I'm the CTO of Coverity, Inc., a company that does static source code 
> analysis to look for defects in code. You may have heard of us or of our 
> technology from its days at Stanford (the "Stanford Checker"). The 
> reason I'm writing is because we have set up a framework internally to 
> continually scan open source projects and provide the results of our 
> analysis back to the developers of those projects. Linux is one of the 
> 32 projects currently scanned at:
> 
> http://scan.coverity.com

Cheers, 
Mauro.


  parent reply	other threads:[~2006-03-14 12:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06  5:35 Coverity Open Source Defect Scan of Linux Ben Chelf
2006-03-06  5:49 ` Dave Jones
2006-03-06 10:27 ` Adrian Bunk
2006-03-06 10:43   ` Bernd Petrovitsch
2006-03-06 11:03     ` Michal Schmidt
2006-03-06 11:08       ` Bernd Petrovitsch
2006-03-06 13:39         ` Ben Chelf
2006-03-06 11:57       ` Gene Heskett
2006-03-06 12:38         ` [OT] Linux washing powder (was: Re: Coverity Open Source Defect Scan of Linux) Michal Schmidt
2006-03-06 20:13           ` Gene Heskett
2006-03-06 13:07         ` Coverity Open Source Defect Scan of Linux Dick Streefland
2006-03-06 13:46   ` Ben Chelf
2006-03-06 15:46 ` Greg KH
2006-03-06 18:33 ` Pavel Machek
2006-03-06 18:53   ` Jesper Juhl
2006-03-14 12:37 ` Mauro Carvalho Chehab [this message]
2006-03-15  3:41 ` Lee Revell

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=1142339844.4667.11.camel@praia \
    --to=mchehab@infradead.org \
    --cc=ben@coverity.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.