If the inquiry cache is empty it makes no sense to return zero number of
inquiry result even if the age of cache is not outdated.

The L2CAP reference counting must be increased by the RFCOMM module if an
incoming connection is accepted. If this is not done, it will be decreased
one time to often if the connection is terminated.

In general a Bluetooth stack that creates an ACL link should also take
care of its termination, but some Bluetooth devices think otherwise. The
problem is that the Bluetooth specification don't defines an ownership
of an ACL link and if nobody cares about it, two devices stay connected
even if there is no need. To avoid leftover ACL links the disconnect
timer must also be used for incoming connections, but it is set twice
the default disconnect timeout so the other side get enough time to
clean everything by itself.

The only possible default value for pscan_rep_mode, if there is no entry
in the inquiry cache, can be R2.

This patch fixes the module reference counting which was done wrong while
porting this driver to the 2.6 kernel series.

This patch changes the interrupt routines to make use of the
irqreturn_t return values.

This adds a driver for the the Broadcom Blutonium USB devices. The devices
with Broadcom chips need a firmware loading sequence before they can work
like any other Bluetooth H:2 USB device.

This patch uses the default ID list to ignore the Broadcom BCM2033 devices
without firmware. If it not handles a device or a interface it now returns
ENODEV to not fill the kernel log with unneeded errors.

This patch adds the missing maintainer entries for the CAPI message
transport protocol and the BlueFRITZ! USB drivers.

This adds support for the CAPI message transport protocol (CMTP)
to the Bluetooth subsystem.

The BlueFRITZ! USB driver must use "select" to enable the firmware
loader, because the option "enable" is deprecated.

This patch adds the missing module alias definitions for the various
Bluetooth protocols.

The module alias for PF_BLUETOOTH was placed in the BNEP module, but it
has to be in the Bluetooth core module.

This adds a driver for the AVM BlueFRITZ! USB devices. The devices
from AVM do not follow the Bluetooth specification part H:2 and thus
they need their own driver.

This patch removes the USB zero packet option from the HCI USB
Bluetooth driver, because it is useless. It also corrects the
config name of the SCO audio support.

The Bluetooth 1.2 specification defines a new event for returning
inquiry results. This patch converts this event into the standard
event and add its information to the inquiry cache.

This patch is a very big update to the HCI security filter. It consists
of every forgotten commands/events from Bluetooth 1.1 and also the new
parts from the Bluetooth 1.2 specification.

This patch adds the specific vendor and product id's for an old
ALPS module which don't uses the USB Bluetooth class id.

The Digianswer USB Bluetooth devices uses a bRequestType of 0x40
for HCI commands, but the Bluetooth specification says that the
correct value is 0x20. This patch sets the needed value according
to the vendor and product id's of the Bluetooth device.

This patch modifies the USB Bluetooth driver to use two ISOC URB's
per RX and TX transfer paths. This is needed for in time transfer
of SCO audio packets over HCI.

The credit based flow control must be disabled by default for compatibility
with Bluetooth 1.0b devices. This patch makes CFC a session attribute,
introduces CFC states and cleans up the CFC logic.

This fixes a bug in the qla1280 driver where it would leave a pointer to
an on the stack completion event in a command structure if
qla1280_mailbox_command fails.  The result is that the interrupt handler
later tries to complete() garbage on the stack.  The mailbox command can
fail if a device on the bus decides to lock up etc.

I just found Yet Another Bug in scsi_ioctl - CDROM_SEND_PACKET puts a
kernel pointer in hdr->cmdp, where sg_io() expects to find user address.
This worked up until recently because of the memcpy bug, but now it
doesn't because we do the proper copy_from_user(). 

This fix undoes the user copy code from sg_io, and instead makes the
SG_IO ioctl copy it locally.  This makes SG_IO and CDROM_SEND_PACKET
agree on the calling convention, and everybody is happy. 

I've tested that both

   cdrecord -dev=/dev/hdc -inq

and

   cdrecord -dev=ATAPI:/dev/hdc -inq

works now.  The former will use SG_IO, the latter CDROM_SEND_PACKET (and
incidentally would work in both 2.4 and 2.6, if it wasn't for
CDROM_SEND_PACKET sucking badly in 2.4).

From Jon Burgess:

  There is a problems with blank DVD media using the ide-cd driver.

  When we attempt to read the blank disk, the drive responds to the read
  request by returning a "blank media" error.  The kernel doesn't have
  any special case handling for this sense value and retries the request
  a couple of times, then gives up and does a bus reset and disables DMA
  to the device.

  Which obviously doesn't help the situation.

  The sense key value of 8 isn't listed in ide-cd.h, but it is listed in
  scsi.h as a "BLANK_CHECK" error.

  This trivial patch treats this error condition as a reason to abort
  the request.  This behaviour is the same as what we do with a blank CD-R.

  It looks like the same fix might be desired for 2.4 as well, although
  is perhaps not so important since scsi-ide is normally used instead.

into home.osdl.org:/home/torvalds/v2.5/linux

 1/ make sure raid5 doesn't try to handle multiple overlaping
    requests at the same time as this would confuse things badly.
    Currently it justs BUGs if this is attempted.
 2/ Fix a possible data-loss-on-write problem.  If two or
    more bio's that write to the same page are processed at the
    same time, only the first was actually commited to storage.
 3/ Fix a use-after-free bug.  raid5 keeps the bio's it is given
    in linked lists when more than one bio touch a single page.
    In some cases the tail of this list can be freed, and
    the current test for 'are we at the end' isn't reliable.
    This patch strengths the test to make it reliable.

Petr Vandrovec noticed a problem where the thread group leader
would not be properly reaped if the parent of the thread group
was ignoring SIGCHLD, and the thread group leader had exited
before the last sub-thread.

Fixed by Ingo Molnar.

This time we have a SMP memory ordering issue in prepare_to_wait(),
where we really need to make sure that subsequent tests for the
event we are waiting for can not migrate up to before the wait
queue has been set up.

In 2.5.x, the BKL was pushed from vfs_readdir() into the filesystem
specific functions.  But only the unlock_kernel() made it into the HPFS
code, lock_kernel() got lost on the way.  This rendered the filesystem
unusable.

This adds the missing lock_kernel().  It's been tested by Timo Maier who
also reported the problem earlier today.

The previous scsi_ioctl.c patch didn't cleanup the buffer/bio in the
error case. 

Fix it by copying the command data earlier.

corruption on SMP because of another CPU still accessing a waitqueue
even after it was de-allocated.

Use a careful version of the list emptiness check to make sure we
don't de-allocate the stack frame before the waitqueue is all done.

into kroah.com:/home/greg/linux/BK/usb-2.6

visor.c defines one empty slot in USB ids table that can be filled in at
runtime using module parameters. file2alias generates catch-all alias for it:

alias usb:v*p*dl*dh*dc*dsc*dp*ic*isc*ip* visor

patch adds the same sanity check as in depmod to scripts/file2alias.

This patch fixes the bug where running ppp over a ttyUSB device would fail.

This patch was integrated by you in 2.4 six months ago.  Unfortunately
it never got into 2.5.  Without it you can end up with crashes such
as http://bugs.debian.org/218670

apart from locking bugs, there are other races. This fixes one with
signal delivery. The signal should be delivered _before_ the reciever
is woken.

this fixes two instances of GFP_KERNEL from completion handlers.