I really don't want to do this, and I was actually hoping to release 
2.6.25 last weekend (which is why -rc9 is a few days late - just me hoping 
to not do another -rc at all), but I've done an -rc9.

The changes in -rc9 are pretty small (shortlog appended), and 60% of them 
are m68k updates - mostly defconfigs. And some doc updates.

But there's some network driver updates (tg3 and wireless hostap stand 
out), some late XFS patches and a mvsas driver update (the mvsas driver is 
new in 2.6.25, so that's not going to regress anything ;).

The rest is mostly one-liners, with a few reverts going on.

Dirstat:

	   4.2% Documentation/filesystems/
	   3.2% Documentation/networking/
	  11.4% Documentation/
	  55.7% arch/m68k/configs/
	  59.4% arch/m68k/
	   2.0% arch/powerpc/
	  65.7% arch/
	   3.6% drivers/net/
	   4.2% drivers/scsi/
	  12.7% drivers/
	   2.3% fs/
	   2.2% include/
	   3.9% net/

anyway, the reason for not doing a 2.6.25 is that some people are making 
noises about slab/page-alloc setup issues, and I wanted something out this 
week, but didn't feel comfy doing a final release.

That said, I think I'll have to do 2.6.25 early next week regardless, 
because we can't just keep holding things back forever. At some point it 
will have to turn into a 2.6.25.x issue, and the developers with stuff 
pending for the next version need to be able to start merging.

			Linus

PS. This has been a somewhat frustrating last week or so. So if I was even 
less polite to somebody than usual in public or private emails, my 
apologies. You know who you are.

---
Abhijeet Kolekar (1):
      iwlwifi: fix n-band association problem

Adrian Bunk (18):
      [ATM]: Make atm/he.c:read_prom_byte() static
      [ATM] atm/idt77252.c: Make 2 functions static
      [NET]: Remove Documentation/networking/sk98lin.txt
      V4L/DVB (7485): v4l2-int-device.c: add MODULE_LICENSE
      ide-pnp.c: add MODULE_LICENSE
      ide/pci/cmd640.c: add MODULE_LICENSE
      ...
[ message continues ]

On Fri, Apr 11, 2008 at 10:51 PM, Linus Torvalds

I just noticed that the following message is printed when I build
2.6.25-rc7 or 2.6.25-rc9 on my system (x86_64):
$ make bzImage
...
WARNING: modpost: Found 26 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
...

The whole list of warnings is as follows:

$ make CONFIG_DEBUG_SECTION_MISMATCH=y bzImage
WARNING: arch/x86/kernel/built-in.o(.data+0x5e0): Section mismatch in
reference from the variable cpu_vsyscall_notifier_nb.11607 to the
function .cpuinit.text:cpu_vsyscall_notifier()
The variable cpu_vsyscall_notifier_nb.11607 references
the function __cpuinit cpu_vsyscall_notifier()
If the reference is valid then annotate the
variable with __init* (see linux/init.h) or name the variable:
*driver, *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,

WARNING: kernel/built-in.o(.text+0x2840b): Section mismatch in
reference from the function take_cpu_down() to the variable
.cpuinit.data:cpu_chain
The function take_cpu_down() references
the variable __cpuinitdata cpu_chain.
This is often because take_cpu_down lacks a __cpuinitdata
annotation or the annotation of cpu_chain is wrong.

WARNING: kernel/built-in.o(.text+0x284a7): Section mismatch in
reference from the function _cpu_down() to the variable
.cpuinit.data:cpu_chain
The function _cpu_down() references
the variable __cpuinitdata cpu_chain.
This is often because _cpu_down lacks a __cpuinitdata
annotation or the annotation of cpu_chain is wrong.

WARNING: kernel/built-in.o(.text+0x284cb): Section mismatch in
reference from the function _cpu_down() to the variable
.cpuinit.data:cpu_chain
The function _cpu_down() references
the variable __cpuinitdata cpu_chain.
This is often because _cpu_down lacks a __cpuinitdata
annotation or the annotation of cpu_chain is wrong.

WARNING: kernel/built-in.o(.text+0x2857a): Section mismatch in
reference from the function _cpu_down() to the ...
[ message continues ]