From: John Cherry <cherry@osdl.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: sparse in compile stats
Date: Thu, 10 Jun 2004 16:42:18 -0700 [thread overview]
Message-ID: <1086910938.5884.79.camel@cherrybomb.pdx.osdl.net> (raw)
In-Reply-To: <20040606191830.GB2788@mars.ravnborg.org>
Sam,
I am doing sparse runs now on all of linus' and andrew's kernels. Since
sparse is changing along with the kernel, comparing to older versions
will not buy us much right now. As sparse stabalizes, perhaps this
would be an option.
For the sparse runs, I am building with allmodconfig (bzImage and
modules).
John
On Sun, 2004-06-06 at 12:18, Sam Ravnborg wrote:
> Hi John.
>
> Recently Al Viro has put in a huge effort into sparse sanitize the kernel,
> and likewise Linus has done several updates to sparse.
> Net result is a _lot_ of sparse warnings removed, and very few (if any?) false positives.
>
> Do you think it is worth to include a sparse run when Linus does next -rc?
> Comparing with older versions should only be for amusement, since Al and Linus did
> such a big effor the last weeks.
>
> Sam
next parent reply other threads:[~2004-06-10 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040606191830.GB2788@mars.ravnborg.org>
2004-06-10 23:42 ` John Cherry [this message]
2004-06-11 21:41 ` Sam Ravnborg
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=1086910938.5884.79.camel@cherrybomb.pdx.osdl.net \
--to=cherry@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®