netdev - Re: pull request: bluetooth-next 2018-12-19

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]

Message-Id: <20181219.084203.649762030333127251.davem@davemloft.net>
Date:   Wed, 19 Dec 2018 08:42:03 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     johan.hedberg@...il.com
Cc:     netdev@...r.kernel.org, linux-bluetooth@...r.kernel.org
Subject: Re: pull request: bluetooth-next 2018-12-19

From: Johan Hedberg <johan.hedberg@...il.com>
Date: Wed, 19 Dec 2018 17:52:46 +0200

> Here's the main bluetooth-next pull request for 4.21:
> 
>  - Multiple fixes & improvements for Broadcom-based controllers
>  - New USB ID for an Intel controller
>  - Support for new Broadcom controller variants
>  - Use DEFINE_SHOW_ATTRIBUTE to simplify debugfs code
>  - Eliminate confusing "last event is not cmd complete" warning message
>  - Added vendor suspend/resume support for H:5 (3-Wire UART) controllers
>  - Various other smaller improvements & fixes
> 
> Please let me know if there are any issues pulling. Thanks.

Pulled, thanks Johan.