From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: pull request: bluetooth-next 2018-12-19 Date: Wed, 19 Dec 2018 08:42:03 -0800 (PST) Message-ID: <20181219.084203.649762030333127251.davem@davemloft.net> References: <20181219155246.GA25077@jhedberg-mac01.local> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org To: johan.hedberg@gmail.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:60926 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727383AbeLSQmE (ORCPT ); Wed, 19 Dec 2018 11:42:04 -0500 In-Reply-To: <20181219155246.GA25077@jhedberg-mac01.local> Sender: netdev-owner@vger.kernel.org List-ID: From: Johan Hedberg 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.