From: "John W. Linville" <linville@tuxdriver.com>
To: Gustavo Padovan <gustavo@padovan.org>,
linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2014-03-24
Date: Thu, 27 Mar 2014 14:18:49 -0400 [thread overview]
Message-ID: <20140327181849.GG31168@tuxdriver.com> (raw)
In-Reply-To: <20140326183411.GB1741@joana>
On Wed, Mar 26, 2014 at 03:34:11PM -0300, Gustavo Padovan wrote:
> Hi John,
>
> 2014-03-24 Gustavo Padovan <gustavo@padovan.org>:
>
> > Hi John,
> >
> > Here follow another set of patches to 3.15. This is mostly a bug fix pull
> > request with the exception of one commit from Marcel which adds tracking to
> > the current configured LE scan type parameter.
>
> There is one more fix that we want to include in this pull request. Here
> follows a new pull request, please pull, Thanks.
>
> Gustavo
>
> --
> The following changes since commit 40b552aa5a0bfa785bc7ddb5c2d7965b1e0bb08d:
>
> Bluetooth: Enforce strict Secure Connections Only mode security (2014-03-19 23:30:32 +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 e8b1ab9e6d30394e0df3e4f60bf56c4dc9bf0863:
>
> Bluetooth: Fix returning peer address in pending connect state (2014-03-26 09:31:33 -0700)
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-03-27 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 17:33 pull request: bluetooth-next 2014-03-24 Gustavo Padovan
2014-03-26 18:34 ` Gustavo Padovan
2014-03-27 18:18 ` 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=20140327181849.GG31168@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=gustavo@padovan.org \
--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).