All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/5] Add support for getting the Encryption Key Size via btio
Date: Thu, 15 Dec 2011 13:37:20 +0200	[thread overview]
Message-ID: <20111215113720.GB6824@x220> (raw)
In-Reply-To: <1323820654-16820-1-git-send-email-vinicius.gomes@openbossa.org>

Hi Vinicius,

On Tue, Dec 13, 2011, Vinicius Costa Gomes wrote:
> --- a/lib/bluetooth.h
> +++ b/lib/bluetooth.h
> @@ -63,6 +63,7 @@ extern "C" {
>  #define BT_SECURITY	4
>  struct bt_security {
>  	uint8_t level;
> +	uint8_t key_size;
>  };
>  #define BT_SECURITY_SDP		0
>  #define BT_SECURITY_LOW		1

This libbluetooth change will need to be in a separate patch since it
needs to be backported to hcidump (which now days has a copy of the lib).

Johan

  parent reply	other threads:[~2011-12-15 11:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 23:57 [PATCH BlueZ 1/5] Add support for getting the Encryption Key Size via btio Vinicius Costa Gomes
2011-12-13 23:57 ` [PATCH BlueZ 2/5] Add support for passing the CID to btiotest Vinicius Costa Gomes
2011-12-13 23:57 ` [PATCH BlueZ 3/5] Add support for btiotest to returning the key size Vinicius Costa Gomes
2011-12-13 23:57 ` [PATCH BlueZ 4/5] Remove the default security level from btio Vinicius Costa Gomes
2011-12-14 11:43   ` Ganir, Chen
2011-12-14 13:56     ` Vinicius Gomes
2011-12-13 23:57 ` [PATCH BlueZ 5/5] Fix btio users to not expect a default security level Vinicius Costa Gomes
2011-12-14 12:09 ` [PATCH BlueZ 1/5] Add support for getting the Encryption Key Size via btio Luiz Augusto von Dentz
2011-12-14 16:35   ` Vinicius Costa Gomes
2011-12-14 17:02 ` Vinicius Costa Gomes
2011-12-15 11:37 ` Johan Hedberg [this message]
2011-12-15 19:18   ` Vinicius Costa Gomes
2012-01-22 20:29     ` Anderson Lizardo
2012-01-23 11:15       ` Johan Hedberg

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=20111215113720.GB6824@x220 \
    --to=johan.hedberg@gmail.com \
    --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.