public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <jdittmer@ppp0.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc4-mm1, build results compared to 2.6.12-rc3-mm3
Date: Thu, 12 May 2005 14:21:02 +0200	[thread overview]
Message-ID: <42834A2E.60908@ppp0.net> (raw)
In-Reply-To: <20050512033100.017958f6.akpm@osdl.org>

Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm1/


Comparing 2.6.12-rc3-mm3 to 2.6.12-rc4-mm1 (defconfig)

- sparc64: broke
    CC      arch/sparc64/kernel/signal32.o
    CC      arch/sparc64/kernel/ioctl32.o
    CC      arch/sparc64/kernel/binfmt_elf32.o
    CC      arch/sparc64/kernel/module.o
    CC      arch/sparc64/kernel/kprobes.o
  In file included from /usr/src/ctest/mm/kernel/arch/sparc64/kernel/kprobes.c:8:
  /usr/src/ctest/mm/kernel/include/linux/kprobes.h:122: error: parse error before "spinlock_t"
  /usr/src/ctest/mm/kernel/include/linux/kprobes.h:123: warning: function declaration isn't a prototype
  make[2]: *** [arch/sparc64/kernel/kprobes.o] Error 1
  make[1]: *** [arch/sparc64/kernel] Error 2
  make: *** [_all] Error 2
  Details: http://l4x.org/k/?d=3653

- arm: fixed
  Details: http://l4x.org/k/?d=3634

- arm26: still broken
  Details: http://l4x.org/k/?d=3635

- cris: still broken
  Details: http://l4x.org/k/?d=3636

- frv: still broken
  Details: http://l4x.org/k/?d=3637

- h8300: still broken
  Details: http://l4x.org/k/?d=3638

- ia64: still broken
  Details: http://l4x.org/k/?d=3640

- m32r: still broken
  Details: http://l4x.org/k/?d=3641

- m68k: still broken
  Details: http://l4x.org/k/?d=3642

- m68knommu: still broken
  Details: http://l4x.org/k/?d=3644

- parisc: still broken
  Details: http://l4x.org/k/?d=3646

- s390: still broken
  Details: http://l4x.org/k/?d=3649

- sh: still broken
  Details: http://l4x.org/k/?d=3650

- sh64: still broken
  Details: http://l4x.org/k/?d=3651

- v850: still broken
  Details: http://l4x.org/k/?d=3655

Summary: 8 ok, 14 failed

-- 
Jan

  reply	other threads:[~2005-05-12 12:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12 10:31 2.6.12-rc4-mm1 Andrew Morton
2005-05-12 12:21 ` Jan Dittmer [this message]
2005-05-13  6:19   ` 2.6.12-rc4-mm1, build results compared to 2.6.12-rc3-mm3 Maneesh Soni
2005-05-12 12:39 ` 2.6.12-rc4-mm1 Reuben Farrelly
2005-05-12 15:09   ` 2.6.12-rc4-mm1 Andrew Morton
2005-05-14 21:19   ` 2.6.12-rc4-mm1 Andrew James Wade
2005-05-12 12:58 ` kobject_register failed for intelfb (-EACCES) (Re: 2.6.12-rc4-mm1) Alexey Dobriyan
2005-05-12 15:43   ` Greg KH
2005-05-12 15:59     ` Andrew Morton
2005-05-12 16:04       ` Greg KH
2005-05-12 16:20       ` Alexey Dobriyan
2005-05-12 18:14 ` [PATCH -mm] Print KBD and AUX irqs correctly Alexey Dobriyan
2005-05-12 21:42 ` [-mm patch] mm.h: fix page_zone compile error Adrian Bunk
2005-05-12 22:09   ` Dave Hansen
2005-05-12 22:26     ` Adrian Bunk
2005-05-13 13:26   ` Andy Whitcroft
2005-05-12 21:54 ` 2.6.12-rc4-mm1 Greg KH
2005-05-13  0:47 ` [-mm patch] drivers/cpufreq/cpufreq_conservative.c: make cpufreq_gov_dbs static Adrian Bunk
2005-05-13  7:24 ` 2.6.12-rc4-mm1 Dave Airlie
2005-05-13  7:25   ` 2.6.12-rc4-mm1 Dave Airlie
2005-05-13 14:53 ` 2.6.12-rc4-mm1 steve
2005-05-13 18:12 ` [-mm patch] kprobes: arch_supports_kretprobes cleanup Frederik Deweerdt
2005-05-13 19:40 ` 2.6.12-rc4-mm1 Johannes Stezenbach
2005-05-14 11:27 ` 2.6.12-rc4-mm1 Richard Purdie
2005-05-16 11:27   ` 2.6.12-rc4-mm2 Richard Purdie
2005-05-15  1:20 ` 2.6.12-rc4-mm1 William Lee Irwin III
2005-05-15  1:30   ` 2.6.12-rc4-mm1 Andrew Morton
2005-05-15  9:44     ` 2.6.12-rc4-mm1 Jesper Juhl
2005-05-15  9:54       ` 2.6.12-rc4-mm1 Andrew Morton
2005-05-15  9:43 ` 2.6.12-rc4-mm1: drivers/usb/gadget/ether.c compile error Adrian Bunk
2005-05-16 15:26   ` David Brownell
2005-05-15 11:32 ` [-mm patch] arch/i386/Kconfig: SELECT_MEMORY_MODEL -> ARCH_SELECT_MEMORY_MODEL Adrian Bunk
2005-05-15 18:24   ` Dave Hansen

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=42834A2E.60908@ppp0.net \
    --to=jdittmer@ppp0.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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