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-10-02
Date: Thu, 2 Oct 2014 13:57:17 -0400 [thread overview]
Message-ID: <20141002175717.GC12208@tuxdriver.com> (raw)
In-Reply-To: <20141002151457.GA3129@t440s.P-661HNU-F1>
On Thu, Oct 02, 2014 at 06:14:57PM +0300, Johan Hedberg wrote:
> Hi John,
>
> Unless 3.17 gets delayed this will probably be our last -next pull request for
> 3.18. We've got:
>
> - New Marvell hardware supportr
> - Multicast support for 6lowpan
> - Several of 6lowpan fixes & cleanups
> - Fix for a (false-positive) lockdep warning in L2CAP
> - Minor btusb cleanup
>
> Please let me know if there are any issues pulling. Thanks.
>
> Johan
>
> ---
> The following changes since commit 565766b087a6d6ff257f5b79c8ceda0188c9169f:
>
> Bluetooth: Rename sco_param_wideband table to esco_param_msbc (2014-09-25 10:35:08 +0200)
>
> 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 9c238ca8ec79c38ab22762b44aeaf7a42fc97b18:
>
> Bluetooth: 6lowpan: Check transmit errors for multicast packets (2014-10-02 13:41:57 +0300)
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-10-02 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 15:14 pull request: bluetooth-next 2014-10-02 Johan Hedberg
2014-10-02 17:57 ` 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=20141002175717.GC12208@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).