into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

Fix so UP does not ask for migration_init

I've got a new i/o scheduler in testing, some changes where needed in
the block layer to accomodate it. Basically because right now
assumptions are made about q->queue_head being the sort list. The
changes in detail:

o elevator_merge_requests_fn takes queue argument as well

o __make_request() inits insert_here to NULL instead of
  q->queue_head.prev, which means that the i/o schedulers must
  explicitly check for this condition now.

o incorporate elv_queue_empty(), it was just a place holder before

o add elv_get_sort_head(). it returns the sort head of the elevator for
  a given request. attempt_{back,front}_merge uses it to determine
  whether a request is valid or not. Maybe attempt_{back,front}_merge
  should just be killed, I doubt they have much relevance with the wake
  up batching.

o call the merge_cleanup functions of the elevator _after_ the merge has
  been done, not before. This way the elevator functions get the new
  state of the request, which is the most interesting.

o Kill extra nr_sectors check in ll_merge_requests_fn()

o bi->bi_bdev is always set in __make_request(), so kill check.

 - Change over queuedata to carry the device instead of the channel
   information.

 - cs5530 patches by Adam J. Richter. Small indent style adjustments.

 - qd65xx cli()/sti() adjustments.

 - Fix bogous command in ide.c pointed out by Peter Vendroviec.

 - Eliminate ide_stall_queue(). For those worried: we didn't sleep at
   all.

 - Eliminate support for "sector remapping". loop devices can handle
   stuff like that. All the custom DOS high system memmory loaded
   BIOS workaround tricks are obsolete right now. If anywhere it should
   be the FAT filesystem code which should be clever enough to deal with
   it by adjusting it's read/write methods.

 - PCI "scather gather" allocation handling revamp by Adam J. Richter.

 - Simplify do_ide_request after ->sleep removal.

 - Make do_ide_request prefer to handle the device matching the request
   queue it was called for first. RQ-queues are unique for devices.
   In a next step queuedata will be changed to point to the device
   not the channel.

Changeset 1.403.142.29 introduces a pretty nasty race into the RPC
code. Once we've decoded the RPC reply, it needs to be protected
against being overwritten by any resends.

The following patch achieves this by ensuring that the request is
removed from the list xprt->recv in xprt_complete_rqst(). This again
ensures that xprt_lookup_rqst() will fail to find that request until
we put it back on the list.

bogus dentry pointer to the VFS layer (which would oops on it
inside the dcache lock).

the d_drop is appropriate.

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

Linus, can we please not have that BUG() in 2.5.30?

One of the flakey things I see with 2.5.29 is that many
devices give trouble enumerating.  uhci still oopses khubd
enumerating pegasus (many control message errors first).
But that's not the only troublesome combo.

This patch fixes a failure that would hang the ohci driver
It's basically avoiding a few less IRQs (most noticable
with ISO), in this case so that a wedged SET_ADDRESS completes.
(Instead of hanging khubd in 'D' state.)  And it also updates
a diagnostic to provide more troubleshooting help for similar
issues in the future.

Linus, please apply. This fixes cpu_possible() on x86.

The following patches to nfs2xdr.c/nfs3xdr.c might be relevant: *entry
points into the page, and so the assignment should be made before we
kunmap().

Also includes a patch that converts references to inode->i_data into
inode->i_mapping.  Not likely to be the source of your hang, but should
still be done for consistency with the rest of the kernel.

One more lookup bug caught. Fix missing unlock_kernel() when doing
readdirplus cached lookups in nfs_lookup().

2.4 kernels were changed to support POSIX thread groups, such that,
sys_getpid() now returns $task->tgid, the thread group id.

Since alpha implements its own getpid syscall, it missed this change,
which is now included here.

This now explains what is really going on much better than before.

symlinks now only use the name field of the struct driver_file_entry, so instead of allocating
a new one each time we want to create one, this changes the API to only accept the name (since
the driverfs core will never use the other fields either)

This also guarantees that we won't leak the memory for the entry when the device goes away:
Since the other entries aren't dynamically allocated, and driverfs doesn't free them, we would
have to free them ourselves. It's not really necessary, so this is another win for us.

Now that all unique information about struct driver_file_entry's are gone (the dentry and parent pointers), 
the data in them is shared among all users of the entry. So, we don't have any reason to dynamically allocate
and duplicate the data anymore.

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-driverfs

copy_process() just copies the process, it doesn't actually start it.

This is in preparation for doing a "atomically start process on CPU X"
or other cases where we want to change the state of the process before
we actually start running it.

Use register_blkdev and unregister_blkdev as before, and everything will work just fine.

Use register_chrdev and unregister_chrdev as before, and everything will work.

 - Include first cut by Adam J. Richter on proper lock protection for
   tuning functions.

 - Rename ide_register_subdriver() to ata_register_device() and
   ide_unregister_subdriver() accordingly to ata_unregister_device(),
   since this is reflecting better what those functions are about.

 - Remove tons of "curicum vite" style useless documentation here and
   there.

 - typedef unsigned char byte; is finally gone. Everything using it should
   be just ported to u8 if I missed some place where it still gets used.

 - Next round of parameter parsing cleanups by Gerald Champagne.
   Adjusted a bit to harmonize with  hd.c.

 - Move IDE register bitfields declarations over from hdparm.h to
   ide.h.

 - Declare constants needed by hd.c directly there. Those are standard
   values not subject to change and we prefer a bit of code duplication
   in favour of making the two drivers independant from each other.

 - Move everything not ioctl related away from hdreg.h to ide.h.
   This header is in effect not private to the ATA code and should
   therefore not contain stuff only usefull there.

The CS5530 one seems unneeded looking at the databook.  Try the patch
below instead, which removes the irq lock and uses the proper kernel
functions to enable MWI and master.

This updates the 2.5.x PC Card drivers of the Bluetooth subsystem.

of the directory itself

to access the struct device, rather than via struct driver_file_entry::parent pointer.

driverfs: Don't put the driver_file_entry in struct inode::u.generic_ip or struct file::private_data
(since it's already in struct dentry::d_fsdata and we always get to that)

for anything useful anymore.

as we don't use the lists anymore

driverfs: Do hashed lookup of dentry's when deleting a driverfs file (instead of searching the list we keep)

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-driverfs

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

using a system call from kernel space. 

This avoids one level of hidden code, and makes what happens
much more explicit (and speeds it up too, fwiw)