linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <padovan@profusion.mobi>
To: Brian Gix <bgix@codeaurora.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC 1/1] Bluetooth: Add LE SecMgr and mgmtops support
Date: Mon, 7 Nov 2011 20:58:36 -0200	[thread overview]
Message-ID: <20111107225836.GA2523@joana> (raw)
In-Reply-To: <4EB854F0.60808@codeaurora.org>

Hi Brian,

* Brian Gix <bgix@codeaurora.org> [2011-11-07 14:00:16 -0800]:

> Implemented missing components of MGMTOPS interface
> Differentiated as needed between BR/EDR pairing and LE pairing
> 
> These are a combination of changes we made to get make MGMTOPS more
> robust, and provide MITM pairing options for LE.  Much work has been
> put into
> merging these changes into the current master branch of Bluetooth Next, but
> they have not been extensively tested on that build.
> 
> This is anticipated to be the first step towards upstreaming these changes,
> 
> Signed-off-by: Brian Gix <bgix@codeaurora.org>
> ---
>  include/net/bluetooth/hci.h      |   36 ++
>  include/net/bluetooth/hci_core.h |   32 ++-
>  include/net/bluetooth/l2cap.h    |    5 +
>  include/net/bluetooth/mgmt.h     |   24 ++-
>  include/net/bluetooth/smp.h      |   14 +-
>  net/bluetooth/hci_conn.c         |   58 +++-
>  net/bluetooth/hci_core.c         |   64 +++-
>  net/bluetooth/hci_event.c        |  166 ++++++---
>  net/bluetooth/hci_sock.c         |    9 +-
>  net/bluetooth/l2cap_core.c       |   15 +-
>  net/bluetooth/mgmt.c             |  743
> ++++++++++++++++++++++++++++++++------
>  net/bluetooth/smp.c              |  661 ++++++++++++++++++++++++---------
>  12 files changed, 1441 insertions(+), 386 deletions(-)

We really appreciate your contribution to upstream, but this need to be
broken in more patches, otherwise its impossible to me review and accept it.

Try to split this in logical and atomic changes, upstream the easiest things
first, like small l2cap or smp changes. New MGMT commands need one commit
for each because they need to be discussed and so on.

The are many examples of this in the mailing list.

	Gustavo

  reply	other threads:[~2011-11-07 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 22:00 [RFC 1/1] Bluetooth: Add LE SecMgr and mgmtops support Brian Gix
2011-11-07 22:58 ` Gustavo Padovan [this message]
2011-11-07 23:07   ` Brian Gix
2011-11-10 12:58 ` Andrei Emeltchenko

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=20111107225836.GA2523@joana \
    --to=padovan@profusion.mobi \
    --cc=bgix@codeaurora.org \
    --cc=linux-bluetooth@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).