Here is another version of the scsi_mid_low_api.txt
document. It adds descriptions of functions supplied
by the mid level for a LLD (lower level driver) to call.
It is also tries to describe the two, alternate
registration scenarios. How do the terms:
"hotplug initialization model" and "passive
initialization model" sound?

After the gendisk changes, the disk name disappeared from the
initialisation methods (sd_spinup et al) because the disk name
is set after the init routines are called.  This moves init to be
after the name is set

it's clearly error-handling specific and allows to mark scsi_new_reset
static

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

into flossy.devel.redhat.com:/usr/local/home/dledford/bk/linus-2.5

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

  request_irq/free_irq are now in linux/interrupt.h

request_irq/free_irq are now in linux/interrupt.h

request_irq/free_irq are now in linux/interrupt.h

request_irq/free_irq are now in linux/interrupt.h

Also fix a printk usage.

dquot that got it implicitly before.

smbfs that got it implicitly before.

pci_hotplug_core that got it implicitly before.

ntfs that got it implicitly before.

jffs2 that got it implicitly before.

intermezzo that got it implicitly before.

hugetlbfs that got it implicitly before.

cifs that got it implicitly before.

quota that got it implicitly before.

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

This patch updates udf to the CVS version:
  - removes UDF_RW
  - fixes a extraneous read after write which killed CDRW performance
  - fixes setting the session
  - fix a array index bug in udf_prealloc_extents
  - fix symlinks to correspond to the UDF spec

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

This introduces the sys_set_thread_address() syscall.  It sets the tid
address (which gets cleared at VM release time) and returns the PID so
that the newly initialized 'initial thread' does not have to do an
additional sys_gettid() call.

It is used to bootstrap a thread group where the original thread user
hasn't had a tid address assigned to it by any parent.

Trivial patch.  We keep a dummy use count for old code which wants to
know its own usecount using GET_USE_COUNT.  It needs to be exported.

Thanks to Doug Ledford for the bug report.

This is the logical counterpoint to the code which marks modules
"[unsafe]" when obsolete (racy) interfaces are used.  Allows "just
remove the damn thing" rmmod -f, and taints the kernel.

Mark it dangerous and experimental in the config file to make this
doubly clear.

This patch implements a generic strcspn.

Sparc64 (and probably others) need all the kernel symbols within
32-bits, which includes the manufactured "__this_module" which refers
to the struct module *.

This changes the interface back to its old style: the arch-specific code
manipulates the init and core sizes, and we call module_alloc() ourselves.

Separates the module loading function prototypes (and elf.h) into
moduleloader.h.  AT_GID in elf.h clashes with xfs.h, but this also
makes module.h less cluttered.

<linux/fs.h> cleanups

memory space it was associated with.

Change from PCI name to generic device name.

The timer code is attempting to replicate the softirq characteristics at
the tasklet level, which is a little pointless.  This patch converts
timers to be a first-class softirq citizen.

fs.h is pulling so much crap in..  No need to include net.h in fs.h if
we move struct sock_alloc to net.h (which already includes fs.h through
skbuf.h and mm.h..).  Fixup the few files in net/ that relied on this,
and the readv/writev implementations that got uio.h through net.h.

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

The "procedure number" has been used for 2 purposes in the kernel
client RPC implementation:

  1) As a number to pass to the server in the RPC header.

  2) As an index into the "procedure array" of type 'struct
     rpc_procinfo', from which the RPC layer can find the XDR
     encode/decode functions, buffer size, and all the other static
     data that it needs to construct the on-wire RPC message.

This works fine for NFSv2, v3 and for the NLM locking code for which
there is a one-to-one mapping between NFS file operations, and RPC
procedures.
For NFSv4 on the other hand, the mapping is many-to-one, since there
is only one RPC procedure number: NFSPROC4_COMPOUND.

For efficiency purposes, we want to have a one-to-one mapping between
NFS file operations and the corresponding XDR encode/decode routines,
but currently this is not possible because of (2). The result is the
mess that is 'struct nfs4_op' and encode/decode_compound.

In the process eliminating (2), we might as well change to passing a
pointer to the appropriate procedure array entry instead of an
index. This change can be made transparent

The appended patch therefore does the following:

   - Substitute a pointer to the rpc_procinfo instead of the RPC
     procedure number in the struct rpc_message.
   - Make the RPC procedure number an entry in the struct
     rpc_procinfo.
   - Clean out the largely unused (except in some obscure lockd
     debugging code) p_name field. The latter was just a stringified
     version of the RPC procedure name, so for those lockd cases, we
     can use the RPC procedure number instead.