mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Ben Chelf" <ben@coverity.com>, linux-kernel@vger.kernel.org
Subject: Re: Coverity Open Source Defect Scan of Linux
Date: Mon, 6 Mar 2006 19:53:16 +0100	[thread overview]
Message-ID: <9a8748490603061053y359c7c8cv3af1d4e16d9bc5a0@mail.gmail.com> (raw)
In-Reply-To: <20060306183318.GA3825@elf.ucw.cz>

On 3/6/06, Pavel Machek <pavel@ucw.cz> wrote:
> On Ne 05-03-06 21:35:11, Ben Chelf wrote:
> > 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
> >
> >   My belief is that we (Coverity) must reach out to the developers of
> > these packages (you) in order to make progress in actually fixing the
> > defects that we happen to find, so this is my first step in that
> > mission. Of course, I think Coverity technology is great, but I want
>
> Could you just open the (kernel) results to the public? Going after
> warnings from compiler (afaics that's roughly what coverity is) is
> ideal janitorial job, and job where many people -- not only core
> developers -- can help.
>                                                                 Pavel

I agree.

Cleaning some of this stuff up is something that I would be prepared
to work on, but I honestly can't be bothered to have to "register"
with coverity for the privilege of seeing the bug-reports...

Linux is a public project, just make the bug-reports/check results
public somewhere so we can all work on them.

--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-03-06 18:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06  5:35 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 [this message]
2006-03-14 12:37 ` Mauro Carvalho Chehab
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=9a8748490603061053y359c7c8cv3af1d4e16d9bc5a0@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=ben@coverity.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®