From: David Miller <davem@davemloft.net>
To: johan.hedberg@gmail.com
Cc: netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2018-12-19
Date: Wed, 19 Dec 2018 08:42:03 -0800 (PST) [thread overview]
Message-ID: <20181219.084203.649762030333127251.davem@davemloft.net> (raw)
In-Reply-To: <20181219155246.GA25077@jhedberg-mac01.local>
From: Johan Hedberg <johan.hedberg@gmail.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.
prev parent reply other threads:[~2018-12-19 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 15:52 pull request: bluetooth-next 2018-12-19 Johan Hedberg
2018-12-19 16:42 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181219.084203.649762030333127251.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox