linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next-2.6 2011-06-21
Date: Tue, 21 Jun 2011 15:54:07 -0300	[thread overview]
Message-ID: <20110621185407.GE2628@joana> (raw)
In-Reply-To: <20110621182024.GD2628@joana>

* Gustavo F. Padovan <padovan@profusion.mobi> [2011-06-21 15:20:24 -0300]:

> Hi John,
> 
> Another batch for 3.1. More L2CAP rewrite patches by myself, now we have an API
> that in the future will allow other pieces like l2cap_sock.c/rfcomm/AMP manager
> to use. It still an unfinished work. We also have here the first bit of the 
> Low Energy Security Manager Protocol by Vinicius Gomes and Another Briglia. And

I meant Anderson Briglia here. Vim autocomplete got me. Sorry.

	Gustavo

      reply	other threads:[~2011-06-21 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 18:20 pull request: bluetooth-next-2.6 2011-06-21 Gustavo F. Padovan
2011-06-21 18:54 ` Gustavo F. Padovan [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=20110621185407.GE2628@joana \
    --to=padovan@profusion.mobi \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).