From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2014-11-27
Date: Mon, 1 Dec 2014 15:50:27 -0500 [thread overview]
Message-ID: <20141201205027.GB7266@tuxdriver.com> (raw)
In-Reply-To: <20141127103606.GA11964@t440s>
On Thu, Nov 27, 2014 at 12:36:06PM +0200, Johan Hedberg wrote:
> Hi John,
>
> Here's one more bluetooth-next pull request for 3.19:
>
> - Minor cleanups for ieee802154 & mac802154
> - Fix for the kernel warning with !TASK_RUNNING reported by Kirill A.
> Shutemov
> - Support for another ath3k device
> - Fix for tracking link key based security level
> - Device tree bindings for btmrvl + a state update fix
> - Fix for wrong ACL flags on LE links
>
> Please let me know if there are any issues pulling. Thanks.
>
> Johan
>
> ---
> The following changes since commit a86c02ea38c53b695209b1181f9e2e18d73eb4e8:
>
> Bluetooth: Add support for Broadcom BCM20702A1 variant (2014-11-18 08:32:14 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git for-upstream
>
> for you to fetch changes up to f6af675ef5489c69fc3d4faf8c6f477df3cbf8b9:
>
> Bluetooth: Automatically flushable packets aren't allowed on LE links (2014-11-27 12:12:27 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2014-12-01 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 10:36 pull request: bluetooth-next 2014-11-27 Johan Hedberg
2014-12-01 20:50 ` John W. Linville [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=20141201205027.GB7266@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).