From: David Miller <davem@davemloft.net>
To: johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2018-01-25
Date: Thu, 25 Jan 2018 16:35:01 -0500 (EST) [thread overview]
Message-ID: <20180125.163501.1972801521632703691.davem@davemloft.net> (raw)
In-Reply-To: <20180125105540.GA28588@x1c.lan>
From: Johan Hedberg <johan.hedberg@gmail.com>
Date: Thu, 25 Jan 2018 12:55:40 +0200
> Here's one last bluetooth-next pull request for the 4.16 kernel:
>
> - Improved support for Intel controllers
> - New set_parity method to serdev (agreed with maintainers to be taken
> through bluetooth-next)
> - Fix error path in hci_bcm (missing call to serdev close)
> - New ID for BCM4343A0 UART controller
>
> Please let me know if there are any issues pulling. Thanks.
Pulled, thanks Johan.
prev parent reply other threads:[~2018-01-25 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 10:55 pull request: bluetooth-next 2018-01-25 Johan Hedberg
2018-01-25 21:35 ` 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=20180125.163501.1972801521632703691.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;
as well as URLs for NNTP newsgroup(s).