All of lore.kernel.org
 help / color / mirror / Atom feed
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 2013-12-10
Date: Wed, 11 Dec 2013 10:55:08 -0500	[thread overview]
Message-ID: <20131211155507.GE7411@tuxdriver.com> (raw)
In-Reply-To: <20131210153830.GA1542@joana>

On Tue, Dec 10, 2013 at 01:38:30PM -0200, Gustavo Padovan wrote:
> Hi John,
> 
> More patches to 3.14. Here we have the support for Low Energy Connection
> Oriented Channels (LE CoC). Basically, as the name says, this adds supports
> for connection oriented channels in the same way we already have them for
> BR/EDR connections so profiles/protocols that work on top of BR/EDR can now
> work on LE plus a plenty of new possibilities for LE.
> 
> Please pull. Thanks!!
> 
> 	Gustavo
> 
> ---
> The following changes since commit 201a5929c8c788f9ef53b010065c9ce70c9c06f0:
> 
>   Bluetooth: Remove dead code from SMP encryption function (2013-12-04 11:09:05 -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 71fb419724fadab4efdf98210aa3fe053bd81d29:
> 
>   Bluetooth: Fix handling of L2CAP Command Reject over LE (2013-12-10 01:15:44 -0800)

Pulling now...

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2013-12-11 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 15:38 pull request: bluetooth-next 2013-12-10 Gustavo Padovan
2013-12-11 15:55 ` 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=20131211155507.GE7411@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.