into kroah.com:/home/greg/linux/BK/gregkh-2.5

into kroah.com:/home/greg/linux/BK/gregkh-2.5

This simple intermezzo Makefile change allows it to build.

OK'ed by Peter Braam.

This fixes the APM GDT entry allocation issue.  Confirmed by Andrew
Morton.

fast system calls. They should now be fully comparable to
traditional system calls.

    Fix SEP stack allocation to look like a real thread stack.
    
    This fixes the "Trap on first sysenter instruction" problem,
    which can happen either as a result of an NMI or a breakpoint
    trap (TF bit set).
    
    Also make the user trampoline save and restore EFLAGS, so that
    the TF bit gets restored after a fast system call (it will have
    been cleared to avoid trap faults in the kernel).

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

into mulgrave.(none):/home/jejb/BK/scsi-for-linus-2.5

 - add support for sending a signal on vblank
 - remove unhelpful AGP chipset strings
 - update radeon texture cache handling

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

into suse.cz:/home/perex/bk/linux-sound/work

into suse.cz:/home/perex/bk/linux-sound/linux-sound

  - intel8x0 - added NVidia NForce2 Audio PCI ID
  - USB driver - clenaups in the disconnect routine
  - added ALSA-Configuration.txt and ControlNames.txt documents

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

  - fixed compilation problem when debug is active

into suse.cz:/home/perex/bk/linux-sound/work

into suse.cz:/home/perex/bk/linux-sound/linux-sound

- some access to urb->hcpriv and urb->status needed to be
   locked using urb->lock
- paranoia: don't depend on two values being in lock-step.

trampoline.

Here's how: we re-load %ebp (arg6) in the kernel sysenter handler
from the stack, and on system call re-play we jump back in user
space to re-initialize %ebp to point to the stack pointer before
re-doing the sysenter instruction.

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

vm86 does broken tasklist scanning for matching task_struct pointers,
which is oopsable. This registers a notifier for it to GC vm86 IRQ's in
release_thread() and removes the broken tasklist scanning.

This bugfix is in 2.4.x and has been in 2.5.x-dj for an extended period
of time.

into kroah.com:/home/linux/linux/BK/gregkh-2.5

into are.twiddle.net:/home/rth/BK/axp-2.5

This patch converts most common hub diagnostics to use the
device model diagnostic macros ... not all, someone should
reduce the number of err() strings for "bogus hub" cases,
and ideally streamline some of the dozen or so "here's what's
special about this new hub" dbg() messages.

So the messages become more useful:  they id the port (and
implicitly the device) involved, using a kernel-wide standard
convention.  Size overhead is smaller too.

For folk running with USB debugging enabled, it also cuts
the useless chatter on connections by deleting the per-poll
success messages and a partial dup message when things change.
And it deletes a newish diagnostic on a (non-hub) unlink path.

It also makes Pete's new debounce message use the right
port number -- one-based, not zero-based.

My main issue with this patch is that it doesn't change
more messages, but it seems reasonable to merge it anyway.

unknown ioctls return -ENOTTY and nothing else.

checking for -EINPROGRESS is wrong.

this makes sure that the kernel thread is dead and gone on module unload.
  - use a completion to wait for the kernel thread's death

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

Don't try to dereference the interrupt endpoint if it doesn't exist.

2.5.50 included a change from -ac which changed MSNDCLAS_HAVE_BOOT and
MSNDPIN_HAVE_BOOT to asked questions. This is wrong (I know since I was
the one who wrote the patch Alan picked up...).

They shouldn't ask questions, the following patch reverts my buggy
change.

The change to eata_pio_proc.c contained a typo: a semicolon instead of a
comma.

elf AUX-table entry.

Move the 'vsyscall' page to 0xffffe000, leaving a hole at the top
of the address space.

Older gcc's do not support that form of ellipsis in a macro.

modern storage boxes support >2TB arrays, but READ CAPACITY
may return 2TB only (with 512 bytes blocksize). According to
SBC, target may return 0xffffffff as device size in order to
notify initiator that device size can't fit into 32 bits and
that initiator should use Long READ CAPACITY with 64bits LBA
field. Following patch implements this logic.