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-09-25
Date: Fri, 26 Sep 2014 13:39:29 -0400 [thread overview]
Message-ID: <20140926173928.GH22967@tuxdriver.com> (raw)
In-Reply-To: <20140925113553.GA9506@t440s.kiipula.fi>
On Thu, Sep 25, 2014 at 02:35:53PM +0300, Johan Hedberg wrote:
> Hi John,
>
> This 3.18 pull request replaces the one I did on Monday ("bluetooth-next
> 2014-09-22", which hasn't been pulled yet). The additions since the last
> request are:
>
> - SCO connection fix for devices not supporting eSCO
> - Cleanups regarding the SCO establishment logic
> - Remove unnecessary return value from logging functions
> - Header compression fix for 6lowpan
> - Cleanups to the ieee802154/mrf24j40 driver
>
> Here's a copy from previous request that this one replaces:
>
> "
> Here are some more patches for 3.18. They include various fixes to the
> btusb HCI driver, a fix for LE SMP, as well as adding Jukka to the
> MAINTAINERS file for generic 6LoWPAN (as requested by Alexander Aring).
>
> I've held on to this pull request a bit since we were waiting for a SCO
> related fix to get sorted out first. However, since the merge window is
> getting closer I decided not to wait for it. If we do get the fix sorted
> out there'll probably be a second small pull request later this week.
> "
>
> Please let me know if there are any issues pulling. Thanks.
>
> Johan
>
> ---
> The following changes since commit 9a783a139c32a905825ee0aa9597f485ea461f76:
>
> Bluetooth: Fix re-setting RPA as expired when deferring update (2014-09-12 18:34:25 +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 565766b087a6d6ff257f5b79c8ceda0188c9169f:
>
> Bluetooth: Rename sco_param_wideband table to esco_param_msbc (2014-09-25 10:35:08 +0200)
Pulling now, but I don't plan to push it back out until Dave pulls my earlier batch...
--
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-09-26 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 11:35 pull request: bluetooth-next 2014-09-25 Johan Hedberg
2014-09-26 17:39 ` 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=20140926173928.GH22967@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).