linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Cherry <cherry@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: 2.6.1-mm4 (compile stats)
Date: Fri, 16 Jan 2004 09:14:06 -0800	[thread overview]
Message-ID: <1074273246.4603.16.camel@cherrytest.pdx.osdl.net> (raw)
In-Reply-To: <20040115225948.6b994a48.akpm@osdl.org>

Linux 2.6 (mm tree) Compile Statistics (gcc 3.2.2)
Warnings/Errors Summary

Kernel            bzImage   bzImage  bzImage  modules  bzImage  modules
                (defconfig) (allno) (allyes) (allyes) (allmod) (allmod)
--------------- ---------- -------- -------- -------- -------- --------
2.6.1-mm4         0w/821e   0w/264e 154w/ 5e   8w/1e   5w/0e    179w/0e
2.6.1-mm3         0w/0e     0w/0e   151w/ 5e  10w/0e   3w/0e    177w/0e
2.6.1-mm2         0w/0e     0w/0e   143w/ 5e  12w/0e   3w/0e    171w/0e
2.6.1-mm1         0w/0e     0w/0e   146w/ 9e  12w/0e   6w/0e    171w/0e
2.6.1-rc2-mm1     0w/0e     0w/0e   149w/ 0e  12w/0e   6w/0e    171w/4e
2.6.1-rc1-mm2     0w/0e     0w/0e   157w/15e  12w/0e   3w/0e    185w/4e
2.6.1-rc1-mm1     0w/0e     0w/0e   156w/10e  12w/0e   3w/0e    184w/2e
2.6.0-mm2         0w/0e     0w/0e   161w/ 0e  12w/0e   3w/0e    189w/0e
2.6.0-mm1         0w/0e     0w/0e   173w/ 0e  12w/0e   3w/0e    212w/0e

Web page with links to complete details:
   http://developer.osdl.org/cherry/compile/

***********************************************************************
For both defconfig and allnoconfig, there are hundreds of the following
warnings:

`CONFIG_X86_L1_CACHE_SHIFT' undeclared here (not in a function)
requested alignment is not a constant

CONFIG_X86_L1_CACHE_SHIFT is not defined in defconfig and allnoconfig.
***********************************************************************

John


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2004-01-16 17:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16  6:59 2.6.1-mm4 Andrew Morton
2004-01-16  9:34 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-21 18:46   ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-21 19:20     ` 2.6.1-mm4 Valdis.Kletnieks
2004-01-16 13:45 ` 2.6.1-mm4 Ed Tomlinson
2004-01-16 17:32   ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 14:49 ` 2.6.1-mm4 Fabian Fenaut
2004-01-16 14:49 ` 2.6.1-mm4 Fabian Fenaut
     [not found] ` <200401161449.i0GEnoAv026627@fire-1.osdl.org>
2004-01-16 17:03   ` 2.6.1-mm4 Andrew Morton
2004-01-16 17:14 ` John Cherry [this message]
2004-01-16 17:37 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 17:58 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 18:17 ` Oops in register_proc_table (2.6.1-mm4) Thomas Schlichter
2004-01-17  2:22 ` 2.6.1-mm4 Adrian Bunk
2004-01-19 11:00 ` 2.6.1-mm4 same sound oops as mm3 Helge Hafting
2004-01-19 11:46 ` 2.6.1-mm4 Luiz Fernando Capitulino
2004-01-20  0:26 ` 2.6.1-mm4 Thomas Molina
2004-01-20  0:57   ` 2.6.1-mm4 Andrew Morton
2004-01-20  2:13     ` 2.6.1-mm4 Thomas Molina

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=1074273246.4603.16.camel@cherrytest.pdx.osdl.net \
    --to=cherry@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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