linux/net/bluetooth/rfcomm, branch v2.6.19

[Bluetooth] Check if RFCOMM session is still attached to the TTY

2006-11-22T00:16:30Z

If the RFCOMM session is no longer attached to the TTY device, then it makes no sense to go through with changing the termios settings. Signed-off-by: Marcel Holtmann

[Bluetooth] Add locking for bt_proto array manipulation

2006-10-16T06:14:34Z

The bt_proto array needs to be protected by some kind of locking to prevent a race condition between bt_sock_create and bt_sock_register. And in addition all calls to sk_alloc need to be made GFP_ATOMIC now. Signed-off-by: Masatake YAMATO Signed-off-by: Frederik Deweerdt Signed-off-by: Marcel Holtmann

[Bluetooth] Check if DLC is still attached to the TTY

2006-10-16T06:14:33Z

If the DLC device is no longer attached to the TTY device, then it makes no sense to go through with changing the termios settings. Signed-off-by: Marcel Holtmann

[Bluetooth] Fix reference count when connection lookup fails

2006-10-16T06:14:32Z

When the connection lookup for the device structure fails, the reference count for the HCI device needs to be decremented. Signed-off-by: Marcel Holtmann

[Bluetooth] Handle return values from driver core functions

2006-10-16T06:14:28Z

Some return values of the driver core register and create functions are not handled and so might cause unexpected problems. Signed-off-by: Marcel Holtmann

[PATCH] const struct tty_operations

2006-10-02T14:57:14Z

As part of an SMP cleanliness pass over UML, I consted a bunch of structures in order to not have to document their locking. One of these structures was a struct tty_operations. In order to const it in UML without introducing compiler complaints, the declaration of tty_set_operations needs to be changed, and then all of its callers need to be fixed. This patch declares all struct tty_operations in the tree as const. In all cases, they are static and used only as input to tty_set_operations. As an extra check, I ran an i386 allyesconfig build which produced no extra warnings. 53 drivers are affected. I checked the history of a bunch of them, and in most cases, there have been only a handful of maintenance changes in the last six months. serial_core.c was the busiest one that I looked at. Signed-off-by: Jeff Dike Acked-by: Alan Cox Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[Bluetooth] Return EINPROGRESS for non-blocking socket calls

2006-09-29T01:01:31Z

In case of non-blocking socket calls we should return EINPROGRESS and not EAGAIN. Signed-off-by: Ulisses Furquim Signed-off-by: Marcel Holtmann

[Bluetooth] Integrate services into the driver model

2006-09-29T01:01:26Z

This patch integrates the services of the Bluetooth protocols RFCOMM, BNEP and HIDP into the driver model. This makes it possible to assign the virtual TTY, network and input devices to a specific Bluetooth connection. Signed-off-by: Marcel Holtmann

[Bluetooth] Correct RFCOMM channel MTU for broken implementations

2006-07-24T19:44:25Z

Some Bluetooth RFCOMM implementations try to negotiate a bigger channel MTU than we can support for a particular session. The maximum MTU for a RFCOMM session is limited through the L2CAP layer. So if the other side proposes a channel MTU that is bigger than the underlying L2CAP MTU, we should reduce it to the L2CAP MTU of the session minus five bytes for the RFCOMM headers. Signed-off-by: Marcel Holtmann

[Bluetooth] Remaining transitions to use kzalloc()

2006-07-12T22:34:28Z

This patch makes the remaining transitions to use kzalloc(). Signed-off-by: Marcel Holtmann