From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Brian Gix <bgix@codeaurora.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>,
Vinicius Costa Gomes <vinicius.gomes@openbossa.org>,
Claudio Takahasi <claudio.takahasi@openbossa.org>
Subject: Re: Low Energy Security Manager
Date: Tue, 5 Apr 2011 22:03:55 -0300 [thread overview]
Message-ID: <20110406010355.GB2279@joana> (raw)
In-Reply-To: <4D9A44A7.4020204@codeaurora.org>
Hi Brian,
* Brian Gix <bgix@codeaurora.org> [2011-04-04 15:22:31 -0700]:
>
> Hi Gustavo,
>
> I (and a few others) are currently doing LE kernel development work off of:
>
> git://gitorious.org/bluetooth-next/for-upstream.git
>
> which is where Vinicius' LE Security Manager resides.
>
> Acceptance of this body of work into bluetooth-next appears to have
> stalled out, and I was wondering if you had a sense for when it may
> start moving forward again. Are there any outstanding comments lodged
> against it? I have looked through the mail reflector, and not seen
> anything that should hold it up, beyond perhaps the normal quiet times
> prior to pushing bluetooth-next changes up the food chain towards the
> official kernel.
The reason is that Marcel also want to review it and he didn't finished his
review it. So things can still changes. We have to be careful on adding new
stuff like a whole layer. If we do something wrong we will have to support
that for years and could be a bad thing. Once Marcel and me finish the review
I will push everything to bluetooth-next. It shouldn't take so long now.
Regards,
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-04-06 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 22:22 Low Energy Security Manager Brian Gix
2011-04-06 1:03 ` Gustavo F. Padovan [this message]
2011-04-06 1:24 ` Vinicius Costa Gomes
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=20110406010355.GB2279@joana \
--to=padovan@profusion.mobi \
--cc=bgix@codeaurora.org \
--cc=claudio.takahasi@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vinicius.gomes@openbossa.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.