diff options
| author | David S. Miller <davem@davemloft.net> | 2012-05-16 01:03:54 -0400 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2012-05-16 01:04:07 -0400 |
| commit | d0cad88d071d59169ac25e5c1e3bee0719a4fccf (patch) | |
| tree | 22f1fc5579b813e1e70b6174354c145cbbb9ac55 /usr | |
| parent | 3ab77bf271e6a41512e366dfa5110edb981ed1d3 (diff) | |
| parent | 60374631487a6dbf6b888729022f0e8d76eec8fb (diff) | |
| download | linux-d0cad88d071d59169ac25e5c1e3bee0719a4fccf.tar.bz2 | |
Merge branch 'for-davem' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless
John Linville says:
Here are three more fixes that some of my developers are desperate to
see included in 3.4...
Johan Hedberg went to some length justifyng the inclusion of these two
Bluetooth fixes:
"The device_connected fix should be quite self-explanatory, but it's
actually a wider issue than just for keyboards. All profiles that do
incoming connection authorization (e.g. headsets) will break without it
with specific hardware. The reason it wasn't caught earlier is that it
only occurs with specific Bluetooth adapters.
As for the security level patch, this fixes L2CAP socket based security
level elevation during a connection. The HID profile needs this (for
keyboards) and it is the only way to achieve the security level
elevation when using the management interface to talk to the kernel
(hence the management enabling patch being the one that exposes this"
The rtlwifi fix addresses a regression related to firmware loading,
as described in kernel.org bug 43187. It basically just moves a hunk
of code to a more appropriate place.
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions