Patch from: john stultz <johnstul@us.ibm.com>

        This patch "fixes" the timer_cyclone code by having it
initialize fast_gettimeoffset_quotient and cpu_khz in the same manner as
timer_tsc. This is required for enabling the timer_cyclone code on the
x440.

Ideally fast_gettimeoffset_quotient would not be used outside timer_tsc
and cpu_khz would be initialized generically outside the timer
subsystem. I have patches to do this, but they touch quite a bit of
generic code, and I'd rather not make the timer_cyclone enablement
(patch to follow) depend on these larger changes.

Patch from: john stultz <johnstul@us.ibm.com>

This cleanup patch makes fast_gettimeoffset_quotient (a timer_tsc specific
variable) static, and replaces its usage with cpu_khz, making it timer_opt
independent.

Patch from: Rusty Lynch <rusty@linux.co.intel.com>

Attempting to cat a sysfs file that returns an error will result in an
endless dump of garbage to the screen because the result of the specific show
operation was being saved to a size_t (unsigned) and then later checked for a
negative value.

Here is a trivial patch to fix the error.

- hugetlbfs_forget_inode() should be using ||

Patch from: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>

Cure imm.c of the recent scsi core damage.

Patch from Neil Brown <neilb@cse.unsw.edu.au>

Initialise the queue's unplug_timer inside blk_queue_make_request.  This
makes the new auto-unplugging more accessable by other clients of
blk_queue_make_request - e.g.  raid5, umem.

This simplifies it and makes it more generic.

into kernel.bkbits.net:/home/vojtech/input

	- work around an undocumented firmware bug
	- fix handling of LED brightness

  the odd addresses for access.

	- relax requirements on devices, joydev now allows joysticks
	  without buttons to work with throttles and pedals, mousedev
	  allows a separate mouse wheel
	- remove a stray semicolon in joydev

	- Fix a bad #define for HID_QUIRK_BADPAD
	- Set absfuzz and absflat for joysticks/gamepads only
	- Add TangTop quirk

	value all the way from an interrupt handler to keyboard.c
	that can display it.

	is a real key and not just a button or something.

from drivers/char/misc.c

	- Fix a possible deadlock with 0xfe resend command (atkbd)
	- Make ->ack variables volatile (they're updated from irq)
	- Fix the GETID one/two byte command to avoid any races
	- Fix Logitech PS2++ extended packet detection
	- Use RESET_BAT on reboot to make notebooks happy

My printf manpage says:

       z      A  following  integer  conversion  corresponds to a
              size_t or ssize_t argument. (Linux libc5 has Z with
              this meaning. Don't use it.)

And the opengroup spec says

z Specifies that a following d , i , o , u , x , or X conversion specifier
  applies to a size_t or the corresponding signed integer type argument; or
  that a following n conversion specifier applies to a pointer to a signed
  integer type corresponding to a size_t argument.


yet our vsnprintf implementation has

				/* 'z' support added 23/7/1999 S.H.    */
				/* 'z' changed to 'Z' --davidm 1/25/99 */


I guess the path of least surprise is to support both.  gcc-3.2.1 doesn't
  seem to care.

The return type of sizeof() is size_t.  On many architectrues size_t is
unsigned long, and may not be printed with %d.  Use %Zu instead.

Need to reenable interrupts around the call to scsi_register(), which blocks.

An anonymous fixed mmap with CONFIG_HUGETLB_PAGE=y will dereference NULL.  We
recur into the pagefault handler with mmap_sem held and lock up.

Patch from Davide Libenzi <davidel@xmailserver.org>

Changes :
 - Timeout overflow check
 - Ceil()ing of ms->jif conversion
 - Syscalls return type int->long

Patch from: Peter Waechtler <pwaechtler@mac.com>

Addresses BUGME bug #331.  "OSS CS4232 nasty spinlock printks on boot"

The locking in some OSS modules is really lousy.
Because save_flags/cli/restore_flags could be used recursivly - the
programmers pushed the locking too far the lower level.

Because on ISA cards the register sets are usually multiplexed
you had to write to an address latch and then access the data port
in an "atomic" manner.

I suggest removing the locking from ad_read/ad_write +
ad_{enter|leave}_MCE and clamping the locks wherever the functions
are called. I hope the attached patch does that correctly.

Yes, I don't like all the timeout loops while holding the locks:
high chances that a cpu is spinning in interrupt context :(

Patch from: David Mosberger <davidm@napali.hpl.hp.com>

Please remember to declare the return-type of syscall stubs as "long".
On 64-bit platforms, it's generally necessary to ensure that the
entire 64-bit return value is valid (and can be checked against
negative values).

Patch from: Frank Davis <fdavis@si.rr.com>

The following addresses bugzilla bug # 340.

Patch from: Frank Davis <fdavis@si.rr.com>

The following patch addresses bugzilla bug # 341.

Patch from: john stultz <johnstul@us.ibm.com>

This patch simply fixes the summit subarch to allow summit kernels to
boot on normal systems.

Someone typed `config' when they meant `conf'.

Also fix a function-defined-but-not-used warning.

This driver is calling down into scsi_register with local interrupts
disabled.  scsi_register performs blocking allocations, starts kernel
threads, etc.  slab debugging gets offended by someone performing blocking
operations with local interrupts disabled.

Patch from Tim Schmielau <tim@physik3.uni-rostock.de>

Converts many open-coded jiffy comparisons to use time_after/before/etc.

Patch from Dipankar Sarma <dipankar@in.ibm.com>

All fs should be using dcache APIs to manipulate dcache hash lists.  This is
in line with the dcache cleanup patch (dcache_rcu-1) from Maneesh that Linus
accepted.  This seems like a reasonable cleanup.  One change though, we don't
need to grab dcache_lock while deleting dentries from the private list and
__d_drop() should suffice here.

make the adaptec driver compile

Patch from Rik van Riel <riel@conectiva.com.br>

the following patch, against today's BK tree, fixes a small
SMP race in disassociate_ctty.  This function gets called
from do_exit, without the BKL held.

However, it sets the *tty variable before grabbing the bkl,
then makes decisions on what the variable was set to before
the lock was grabbed, despite the fact that another process
could modify its ->tty pointer in this same function.

Patch from Oleg Drokin <green@namesys.com>, Nikita Danilov <Nikita@Namesys.COM>

There is no uniprocessor definition of _raw_write_trylock(), so
write_trylock() doesn't work on UP.