linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Andre Guedes <andre.guedes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC v3 1/5] Bluetooth: Add address type to struct sockaddr_l2
Date: Thu, 05 Apr 2012 10:49:39 -0700	[thread overview]
Message-ID: <1333648179.16897.16.camel@aeonflux> (raw)
In-Reply-To: <1333646241-12574-2-git-send-email-andre.guedes@openbossa.org>

Hi Andre,

> This patch adds the address type info to struct sockaddr_l2 so
> user-space can inform the remote device address type required
> to establish LE connections.
> 
> Soon, instead of looking the advertising cache up to discover the
> address type, we'll use this address type info to establish LE
> connections.
> 
> Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
> ---
>  include/net/bluetooth/l2cap.h |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
> index f6f0500..d14967e 100644
> --- a/include/net/bluetooth/l2cap.h
> +++ b/include/net/bluetooth/l2cap.h
> @@ -57,6 +57,7 @@ struct sockaddr_l2 {
>  	__le16		l2_psm;
>  	bdaddr_t	l2_bdaddr;
>  	__le16		l2_cid;
> +	__u8		l2_bdaddr_type;
>  };

so I am trying to come up with a better name for this value. It feels a
little bit too long to me.

I was considering l2_bdtype, but that is not really semantically correct
here. Or would it be fine? We could do l2_bdatype, but that does not
really make it any better either.

Regards

Marcel



  reply	other threads:[~2012-04-05 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 17:17 [RFC v3 0/5] LE Connection Andre Guedes
2012-04-05 17:17 ` [RFC v3 1/5] Bluetooth: Add address type to struct sockaddr_l2 Andre Guedes
2012-04-05 17:49   ` Marcel Holtmann [this message]
2012-04-05 22:18     ` Andre Guedes
2012-04-24 16:42       ` Andre Guedes
2012-04-24 17:04         ` Marcel Holtmann
2012-04-05 17:17 ` [RFC v3 2/5] Bluetooth: Move address type macros to bluetooth.h Andre Guedes
2012-04-05 17:17 ` [RFC v3 3/5] Bluetooth: Add dst_type parameter to hci_connect Andre Guedes
2012-04-05 17:17 ` [RFC v3 4/5] Bluetooth: Use address type info from User-space Andre Guedes
2012-04-05 17:17 ` [RFC v3 5/5] Bluetooth: Remove advertising cache Andre Guedes

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=1333648179.16897.16.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=andre.guedes@openbossa.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).