Re: RFD: Kernel release numbering

[Jan Dittmer]

Russell King wrote:
> On Sat, May 07, 2005 at 12:51:41PM +0200, Jan Dittmer wrote:
> 
>>Sorry for tapping in so late. I don't follow lkml that close. For some time
>>I thought about providing semi-automatic mails of what architectures broke/
>>got fixed from one version to another, tracking mm/rc/git(?). Would that
>>be useful?
> 
> 
> We have http://armlinux.simtec.co.uk/kautobuild/ setup for ARM -
> it would be nice if it could generate mail reports and send them
> out, especially when failures occur.
> 
> I think it would need some post-processing and rate limiting to
> determine if there is a common problem across multiple platforms
> (eg, 40 builds failing due to rd_size), or just one platform (some
> local breakage).

Well I built something like this now which I mail to myself,
overlook and then going sent to lkml:

Comparing 2.6.12-rc3-mm2 to 2.6.12-rc3-mm3 (defconfig)

- arm: broke
    AR      arch/arm/lib/lib.a
    GEN     .version
    CHK     include/linux/compile.h
    UPD     include/linux/compile.h
    CC      init/version.o
    LD      init/built-in.o
    LD      .tmp_vmlinux1
  arch/arm/kernel/built-in.o(.init.text+0xb64): In function `$a':
  : undefined reference to `rd_size'
  make[1]: *** [.tmp_vmlinux1] Error 1
  make: *** [_all] Error 2
  Details: http://l4x.org/k/?d=3476

- m32r: broke
  : relocation truncated to fit: R_M32R_26_PCREL_RELA pcibus_to_node
  drivers/built-in.o(.text+0x46258): In function `init_irq':
  : undefined reference to `pcibus_to_node'
  drivers/built-in.o(.text+0x46258): In function `init_irq':
  : relocation truncated to fit: R_M32R_26_PCREL_RELA pcibus_to_node
  drivers/built-in.o(.text+0x4a15c): In function `idedisk_attach':
  : undefined reference to `pcibus_to_node'
  drivers/built-in.o(.text+0x4a15c): In function `idedisk_attach':
  : relocation truncated to fit: R_M32R_26_PCREL_RELA pcibus_to_node
  make[1]: *** [vmlinux] Error 1
  make: *** [_all] Error 2
  Details: http://l4x.org/k/?d=3483

- ppc: fixed

- um: fixed

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

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

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

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

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

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

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

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

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

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

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

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

Summary: 8 ok, 14 failed
Link to this page: http://l4x.org/k/?diff[v1]=mm

-- 
Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/