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 2017-08-01
Date: Tue, 01 Aug 2017 17:43:38 -0700 (PDT) [thread overview]
Message-ID: <20170801.174338.1066495009711747378.davem@davemloft.net> (raw)
In-Reply-To: <20170801094156.GA22557@x1c.lan>
From: Johan Hedberg <johan.hedberg@gmail.com>
Date: Tue, 1 Aug 2017 12:41:56 +0300
> Here's our first batch of Bluetooth patches for the 4.14 kernel:
>
> - Several new USB IDs for the btusb driver
> - Memory leak fix in btusb driver
> - Cleanups & fixes to hci_nokia, hci_serdev and hci_bcm drivers
> - Fixed cleanup path in mrf24j40 (802.15.4) driver probe function
> - A few other smaller cleanups & fixes to drivers
>
> Please let me know if there are any issues pulling. Thanks.
Pulled, thank you.
prev parent reply other threads:[~2017-08-02 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 9:41 pull request: bluetooth-next 2017-08-01 Johan Hedberg
2017-08-02 0:43 ` 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=20170801.174338.1066495009711747378.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).