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-10-21
Date: Tue, 5 Nov 2013 15:50:55 -0500	[thread overview]
Message-ID: <20131105205055.GE8264@tuxdriver.com> (raw)
In-Reply-To: <20131021223736.GA2043@joana>

On Mon, Oct 21, 2013 at 08:37:36PM -0200, Gustavo Padovan wrote:
> Hi John,
> 
> One more big pull request for 3.13. These are the patches we queued during
> last week. Here you will find a lot of improvements to the HCI and L2CAP and
> MGMT layers with the main ones being a better debugfs support and end of work
> of splitting L2CAP into Core and Socket parts.
> 
> Please pull!
> 
> 	Gustavo
> 
> ---
> The following changes since commit 4b836f393bd8ed111857a6ee1865e44627266ec6:
> 
>   Bluetooth: Read current IAC LAP on controller setup (2013-10-14 19:31:18 -0300)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next for-upstream
> 
> for you to fetch changes up to d78a32a8fcf775111ccc9ba611a08ca5c29784b6:
> 
>   Bluetooth: Remove sk member from struct l2cap_chan (2013-10-21 13:50:56 -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.

      reply	other threads:[~2013-11-05 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 22:37 pull request: bluetooth-next 2013-10-21 Gustavo Padovan
2013-11-05 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=20131105205055.GE8264@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.