Tridge has written a little utility
(http://samba.org/ftp/unpacked/junkcode/findstatic.pl) that (given a set of
object files) works out a list of candidate finctions and variables that
may be able to be made static.  Obviously some hand checking is needed
(different configs and/or architectures etc), but it seems useful.

Here is my first patch using its outout.

kstack_depth_to_print is used in many architectures, but only in one
file in each.  In some architectures it is declared and not used.  It
is not even clear why kstack_depth_to_print is not a #define.  Tridge
suggested that maybe you could change its value with a debugger ...

The APM code has a function and a struct that can be static.

Strictly speaking, this patch is needed only for arches which use
discontiguous virtual address bits for the PGD index.

When we originally worked on this code (~ 2 years ago or so, in
response to a bug report & patch from an Intel guy), I had myself
convinced that the code is correct, but of course I missed the fact
that:

	pgd_index(first) < pgd_index(last)

does NOT imply that:

	first < last

For example, with a 16KB page size on ia64, we might end up with:

   first = 6000100f80003fff => first_idx = 0x300
   last  = 60000fffffff8000 =>  last_idx = 0x3ff

Note here that first_idx < last_idx even though first > last.  This is
because pgd_index() ignores bits 44..60.

I suppose we could put the extra check inside #ifdef __ia64__, but
that would be rather ugly and would really mean that Linux does not
support discontiguous PGD indices.

For an SMP kernel, spin_lock() et.al. are functions.
For a UP kernel, they are statements that must be terminated
by a ';'.  This is not quite the same thing, and hence spin_lock()
cannot be using inside a parenthesised expession.

This patch changes ITERATE_MDDEV to use gcc's "statement expressions"
instead which has the benefit of making the conditionals
more readable.

When we abort a resync before we even started (because we were
interrupted while waiting for a conflicting resync to finish)
we should not wait or, particularly, do the closing sync_request
(as we haven't even calculated max_sectors yet).

... as autostart_array does it's own locking.


 ----------- Diffstat output ------------
 ./drivers/md/md.c |   26 ++++++++++++++------------
 1 files changed, 14 insertions(+), 12 deletions(-)

into home.transmeta.com:/home/torvalds/v2.5/linux

This upgrades the fusion driver

 - Provides support for the Ultra320 1030/1020 parts
 - Provides support for the PCI-X FC parts (919X/929X)
 - Provides proper support for high memory cases
 - Provides IA64 support
 - Adds kernels calls (pci_enable_device, pci_set_dma_mask,
   scsi_set_pci_device) for proper registration of PCI devics.
 - Adds New Error Handling support

Removes CM206_BH (patch approved by maintainer).
Deletes the no-longer-used BH entries from the enum.  Explicit numbers
added so as not to destroy binary compatibility needlessly.

into home.transmeta.com:/home/torvalds/v2.5/linux

 - Revert patch number 92. It turned out to be broken behind hope.  Personally I
   attribute this to the recent heat wave over here and apologize for the
   problems this may have caused. Turned out that my note about the change
   beeing dnagerous in the last change log was more then true...

 - Locking issues for ioctl handling.

 - Remove waiting_for_dma bit field. Use IDE_DMA bit flag instead.
   Apply this bit globally and not in the corresponding implementation
   functions.

into home.transmeta.com:/home/torvalds/v2.5/linux

into home.transmeta.com:/home/torvalds/v2.5/linux

into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5

into elte.hu:/home/mingo/BK/linux-2.5-sched

- Add check at mount time to verify that the number of inodes on the
  volume does not exceed 2^32 - 1, which is the maximum allowed for
  NTFS according to Microsoft.
- Change mft_no member of ntfs_inode structure to be unsigned long.
  Update all users. This makes ntfs_inode->mft_no just a copy of struct
  inode->i_ino. But we can't just always use struct inode->i_ino and
  remove mft_no because extent inodes do not have an attached struct
  inode.

  new hot-pluggable CPU enumeration method, and the possibility
  to not boot on CPU#0.

(btw., i find RR's comment offensive. How can any code be called 'crap' just
because the author of a new patch has not converted the code to the new
assumptions yet? The original code was perfectly valid.)

- Remove unused variables left over after Rusty's patch to the decompression
  engine.
- Change buffer size in ntfs_readdir()/ntfs_filldir() to use
  NLS_MAX_CHARSET_SIZE.
- Miscellaneous minor cleanups to comments.

* fix big endia multi-cast filtering
* fix 8139too ethtool media interface

into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5

into home.transmeta.com:/home/torvalds/v2.5/linux

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make

into home.transmeta.com:/home/torvalds/v2.5/linux

So the missing EXPORT_SYMBOL() for ioremap_nocache at least found
some ISDN drivers which shouldn't have been using it in the first
place.

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn

This patch adds the PCMCIA client driver for the AVM A1/Fritz!PCMCIA
ISDN cards, which has been in 2.4 for some time already.

This fixes linux/tqueue.h compile errors in 2.5.23 that were
found by Andy Pfiffer, Matthew Harrell and me.

into home.transmeta.com:/home/torvalds/v2.5/linux

Submitted by Thunder

fsync is allowed to return early if datasync is set and the I_DIRTY_DATASYNC
flags is cleared, not if either of those is true.

Submitted by Christoph Hellwig

I've got to keep my 2.4 and 2.5 patches straight!