From: Greg KH <greg@kroah.com>
To: dan carpenter <error27@email.com>
Cc: linux-kernel@vger.kernel.org, smatch-discuss@lists.sourceforge.net
Subject: Re: smatch update / 2.5.64 / kbugs.org
Date: Wed, 5 Mar 2003 23:42:11 -0800 [thread overview]
Message-ID: <20030306074211.GA719@kroah.com> (raw)
In-Reply-To: <20030306073727.2806.qmail@email.com>
On Thu, Mar 06, 2003 at 02:37:27AM -0500, dan carpenter wrote:
> /*
> * Smatch is an open source c error checker based
> * on the papers about the Stanford Checker.
> * (http://smatch.sf.net) The documentation on coding
> * smatch checks has been updated since my last email to
> * this list.
> *
> */
>
> The smatch bugs for kernel 2.5.64 are up. The
> new url for the smatch bug database is http://kbugs.org.
I really appreciate the work you are doing on this project, but I have a
comment on how the output is being generated.
What I really need to know is, what are all of the reported errors in a
specific portion of the kernel tree. If you give some way to search
based on filename and path, I think you will find a lot more people
using the results of this tool. I know I would :)
Also, what advantage does signing up for a user account on the kbugs.org
site give you?
thanks,
greg k-h
next prev parent reply other threads:[~2003-03-06 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 7:37 smatch update / 2.5.64 / kbugs.org dan carpenter
2003-03-06 7:42 ` Greg KH [this message]
2003-03-06 15:37 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 8:15 dan carpenter
2003-03-07 6:45 dan carpenter
2003-03-07 6:53 ` Oleg Drokin
2003-03-14 8:25 ` Oleg Drokin
2003-03-07 8:32 dan carpenter
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=20030306074211.GA719@kroah.com \
--to=greg@kroah.com \
--cc=error27@email.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smatch-discuss@lists.sourceforge.net \
/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.