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 2015-11-05
Date: Thu, 05 Nov 2015 11:38:52 -0500 (EST) [thread overview]
Message-ID: <20151105.113852.1180740055846209439.davem@davemloft.net> (raw)
In-Reply-To: <20151105061929.GA599@t440s.P-661HNU-F1>
From: Johan Hedberg <johan.hedberg@gmail.com>
Date: Thu, 5 Nov 2015 08:19:29 +0200
> The following set of Bluetooth patches would be good to get into 4.4-rc1
> if possible:
>
> - Fix for missing LE CoC parameter validity checks
> - Fix for potential deadlock in btusb
> - Fix for issuing unsupported commands during HCI init
>
> Please let me know if there are any issues pulling. Thanks.
Pulled, thanks Johan.
prev parent reply other threads:[~2015-11-05 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 6:19 pull request: bluetooth 2015-11-05 Johan Hedberg
2015-11-05 16:38 ` 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=20151105.113852.1180740055846209439.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).