From: John Cherry <cherry@osdl.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.63
Date: 24 Feb 2003 14:32:19 -0800 [thread overview]
Message-ID: <1046125939.18438.99.camel@cherrytest.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0302241127050.13335-100000@penguin.transmeta.com>
Compile statistics: 2.5.63
Note that gcc 3.2 was used for all of these statistics.
2.5.62 2.5.63
-------------------- -----------------
bzImage (defconfig) 18 warnings 15 warnings
0 errors 0 errors
bzImage (allmodconfig) 33 warnings 29 warnings
9 errors 9 errors
modules (allmodconfig) 2514 warnings 2426 warnings
105 errors 128 errors
Compile statistics have been for kernel releases from 2.5.46 to 2.5.63
at: www.osdl.org/archive/cherry/stability
I am also compiling nightly views of Linus' linux-2.5 bitkeeper tree.
Results can be found at:
www.osdl.org/archive/cherry/stability/linus-tree/running.txt
John
next prev parent reply other threads:[~2003-02-24 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 19:32 Linus Torvalds
2003-02-24 20:10 ` Christoph Hellwig
2003-02-24 20:30 ` Christoph Hellwig
2003-02-26 2:08 ` george anzinger
2003-02-24 22:11 ` Linux 2.5.63 [kernel BUG at drivers/net/tulip/de2104x.c:925!] Remco Post
2003-02-24 22:32 ` John Cherry [this message]
2003-02-25 13:15 ` 2.5.63: fore200e.c doesn't compile Adrian Bunk
2003-02-25 14:45 ` chas williams
[not found] ` <200302251453.h1PErvGi030679@locutus.cmf.nrl.navy.mil>
2003-02-25 15:44 ` Adrian Bunk
2003-02-25 14:09 ` Linux 2.5.63 - nfs mount fails Helge Hafting
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=1046125939.18438.99.camel@cherrytest.pdx.osdl.net \
--to=cherry@osdl.org \
--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
all inboxes | Powered by JetHome®