make device_remove_file take a struct device_attribute *, instead of just 
a char * (for consistency with device_create_file)

API is just about to change...)

do a s/driver_file_entry/device_attribute/g on all of them.

It may seem gratuitous, but it's what we really want. 

driverfs files are meant to expose attributes of various kernel objects, so in that sense,
the change adds more accurate meaning to the object.

Plus, we will soon gain the ability to expose attributes of drivers (both device and bus) 
themselves, and we want to be able to have each mean something reasonable.

This changes driverfs and the device model core (but none of the other users)

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.

 - 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)

This "warning fix" bug report is actually an OOPS bugfix.

locks_unlock_delete is buggy in a couple of different ways (previously
reported by Brian Dixon). Rather than fix it, this patch simply deletes
it and uses the normal posix file locking mechanisms to remove all locks
in locks_remove_posix instead.

Make cpu_relax() on all architectures a gcc barrier to match x86.

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

o Corrected dependencies for parportbook
o Introduced do_cmd, thus adhering to KBUILD_VERBOSE and make -s

do_cmd is a nice shorthand when creating rules that in one line
shall adhere to KBUILD_VERBOSE and make -s.
So far the only user is (will be) the docbook makefile

file locking LSM update

An acct flag was added to do_munmap, true everywhere but in mremap's
move_vma: instead of updating the arch and driver sources, revert that
that change and temporarily mask VM_ACCOUNT around that one do_munmap.

Also, noticed that do_mremap fails needlessly if both shrinking _and_
moving a mapping: update old_len to pass vm area boundaries test.

If we support mmap MAP_NORESERVE, we should support it on shared
anonymous objects: too bad that needs a few changes.  do_mmap_pgoff pass
VM_ACCOUNT (or not) down to shmem_file_setup, flag stored into shmem
info, for use by shmem_delete_inode later.  Also removed a harmless but
pointless call to shmem_truncate.

Update Doc and remove FIXME comment from fork.c now accounting right.

do_mmap_pgoff's (file == NULL) check was incorrect: it caused shared
MAP_ANONYMOUS objects to be counted twice (again in shmem_file_setup),
and again on fork(); whereas the equivalent shared /dev/zero objects
were correctly counted.  Conversely, a private readonly file mapping
was (correctly) not counted, but still not counted when mprotected to
writable: mprotect_fixup had pointless "charged = 0" changes, now it
does vm_enough_memory checking when private is first made writable
(but later we may want to refine behaviour on a noreserve mapping).

Also changed correct (flags & MAP_SHARED) test in do_mmap_pgoff to
equivalent (vm_flags & VM_SHARED) test: because do_mmap_pgoff is
dealing with vm_flags rather than the input flags by that stage.

Remove vm_unacct_vma function: it's only used in one place,
which can do it better by using vm_unacct_memory directly.

do_mmap_pgoff clears MAP_NORESERVE from vm_flags when VM accounts
strictly: but it's not in vm_flags, it's in flags (and tested there).