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-09-30
Date: Tue, 02 Oct 2018 22:35:30 -0700 (PDT) [thread overview]
Message-ID: <20181002.223530.974704352661128773.davem@davemloft.net> (raw)
In-Reply-To: <20180930073636.GA25786@x1c.home>
From: Johan Hedberg <johan.hedberg@gmail.com>
Date: Sun, 30 Sep 2018 10:36:36 +0300
> Here's the first bluetooth-next pull request for the 4.20 kernel.
>
> - Fixes & cleanups to hci_qca driver
> - NULL dereference fix to debugfs
> - Improved L2CAP Connection-oriented Channel MTU & MPS handling
> - Added support for USB-based RTL8822C controller
> - Added device ID for BCM4335C0 UART-based controller
> - Various other smaller cleanups & fixes
>
> Please let me know if there are any issues pulling. Thanks.
Pulled, thanks.
prev parent reply other threads:[~2018-10-03 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 7:36 pull request: bluetooth-next 2018-09-30 Johan Hedberg
2018-10-03 5: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=20181002.223530.974704352661128773.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).