linux-kernel - Re: pull request: bluetooth-next 2014-11-27

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 1 Dec 2014 15:50:27 -0500
From:	"John W. Linville" <linville@...driver.com>
To:	linux-wireless@...r.kernel.org, linux-bluetooth@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: pull request: bluetooth-next 2014-11-27

On Thu, Nov 27, 2014 at 12:36:06PM +0200, Johan Hedberg wrote:
> Hi John,
> 
> Here's one more bluetooth-next pull request for 3.19:
> 
>  - Minor cleanups for ieee802154 & mac802154
>  - Fix for the kernel warning with !TASK_RUNNING reported by Kirill A.
>    Shutemov
>  - Support for another ath3k device
>  - Fix for tracking link key based security level
>  - Device tree bindings for btmrvl + a state update fix
>  - Fix for wrong ACL flags on LE links
> 
> Please let me know if there are any issues pulling. Thanks.
> 
> Johan
> 
> ---
> The following changes since commit a86c02ea38c53b695209b1181f9e2e18d73eb4e8:
> 
>   Bluetooth: Add support for Broadcom BCM20702A1 variant (2014-11-18 08:32:14 +0100)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git for-upstream
> 
> for you to fetch changes up to f6af675ef5489c69fc3d4faf8c6f477df3cbf8b9:
> 
>   Bluetooth: Automatically flushable packets aren't allowed on LE links (2014-11-27 12:12:27 +0200)

Pulling now...

-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/