From: dan carpenter <d_carpenter@sbcglobal.net>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel-janitor-discuss@lists.sourceforge.net
Subject: Re: [2.5] [Cool stuff] "checking" mode for kernel builds
Date: Mon, 26 May 2003 15:17:04 +0200 [thread overview]
Message-ID: <200305261517.05613.d_carpenter@sbcglobal.net> (raw)
In-Reply-To: <3ED2BE4D.4080005@gmx.net>
On Tuesday 27 May 2003 03:24 am, Carl-Daniel Hailfinger wrote:
> > Most people who have used the tool actually like how it forces you to
> > make it very _explicit_ whether you're using a user pointer or not. But I
> > have to admit that I've grown tired of trying to look at all the uses and
> > making sure which sparse warnings are valid and which aren't.
>
> Dan? IIRC you have tools to tackle this issue in a distributed manner.
>
>
Tracking bugs from one version to the next works pretty well for kbugs.org.
Anyone can moderate the bugs as real or not. I haven't used sparse script
yet, but I'll do that tomorrow. I'd be happy to post the results on
kbugs.org. :)
regards,
dan carpenter
next prev parent reply other threads:[~2003-05-27 6:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 0:17 [2.5] [Cool stuff] "checking" mode for kernel builds Carl-Daniel Hailfinger
2003-05-27 0:25 ` John Anthony Kazos Jr.
2003-05-27 0:36 ` Linus Torvalds
2003-05-27 1:24 ` Carl-Daniel Hailfinger
2003-05-26 13:17 ` dan carpenter [this message]
2003-05-27 1:58 ` Miles Bader
2003-05-27 3:02 ` Aaron Lehmann
2003-05-27 3:23 ` Linus Torvalds
2003-05-27 4:47 ` Aaron Lehmann
2003-05-27 5:07 ` Linus Torvalds
2003-05-27 9:16 ` Ryan Anderson
2003-05-27 14:44 ` Linus Torvalds
2003-05-27 11:03 ` dep
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=200305261517.05613.d_carpenter@sbcglobal.net \
--to=d_carpenter@sbcglobal.net \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=kernel-janitor-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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