All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv6 hcidump 2/4] add fixed channel definitions
Date: Fri, 21 Oct 2011 11:36:53 +0300	[thread overview]
Message-ID: <20111021083653.GA1800@fusion.localdomain> (raw)
In-Reply-To: <1319099414-27993-3-git-send-email-Andrei.Emeltchenko.news@gmail.com>

Hi Andrei,

On Thu, Oct 20, 2011, Emeltchenko Andrei wrote:
> ---
>  lib/l2cap.h |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/lib/l2cap.h b/lib/l2cap.h
> index 47b3dc3..3880551 100644
> --- a/lib/l2cap.h
> +++ b/lib/l2cap.h
> @@ -139,6 +139,11 @@ struct l2cap_conninfo {
>  
>  #define L2CAP_SDULEN_SIZE	2
>  
> +/* L2CAP fixed channels */
> +#define L2CAP_FC_L2CAP		0x02
> +#define L2CAP_FC_CONNLESS	0x04
> +#define L2CAP_FC_A2MP		0x08
> +
>  /* L2CAP structures */
>  typedef struct {
>  	uint16_t	len;

The first two patches have been applied.

For the rest, like Marcel suggested, I think it'd be a good idea to have
proper get_{le,be}{16,32,64} functions. Since we can use these both in
hcidump and bluez I suppose libbluetooth is the appropriate place for
them, however in that case (e.g. if you put them in lib/bluetooth.h) a
_bt prefix should be added.

Johan

  reply	other threads:[~2011-10-21  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20  8:30 [PATCHv6 hcidump 0/4] decode fixed channels Emeltchenko Andrei
2011-10-20  8:30 ` [PATCHv6 hcidump 1/4] add btohll macro Emeltchenko Andrei
2011-10-20  8:30 ` [PATCHv6 hcidump 2/4] add fixed channel definitions Emeltchenko Andrei
2011-10-21  8:36   ` Johan Hedberg [this message]
2011-10-21 10:48     ` Emeltchenko Andrei
2011-10-23 20:32       ` Johan Hedberg
2011-10-20  8:30 ` [PATCHv6 hcidump 3/4] get_uint64 helper Emeltchenko Andrei
2011-10-20  8:30 ` [PATCHv6 hcidump 4/4] decode fixed channel list info rsp Emeltchenko Andrei

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=20111021083653.GA1800@fusion.localdomain \
    --to=johan.hedberg@gmail.com \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --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 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.