All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mat Martineau <mathewm@codeaurora.org>
To: Ulisses Furquim <ulisses@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org, padovan@profusion.mobi,
	pkrystad@codeaurora.org, marcel@holtmann.org,
	luiz.dentz@gmail.com, andrei.emeltchenko.news@gmail.com
Subject: Re: [RFC 1/2] Bluetooth: Header changes for ERTM state machine replacement
Date: Fri, 24 Feb 2012 16:32:15 -0800	[thread overview]
Message-ID: <4F482C0F.8000305@codeaurora.org> (raw)
In-Reply-To: <CAA37ikZRndo-Sk5r5Dfv64rB9ehdCJLVzYGuGfOCy+VmLX4c7Q@mail.gmail.com>

Ulisses -

On 2/24/2012 9:39 AM, Ulisses Furquim wrote:
> Hi Mat,
>
> On Thu, Feb 23, 2012 at 6:37 PM, Mat Martineau<mathewm@codeaurora.org>  wrote:
>> This change affects data structures storing ERTM state and control
>> fields, and adds new definitions for states and events.  An
>> l2cap_seq_list structure is added for tracking ERTM sequence numbers
>> without repeated memory allocations.  Control fields are carried in
>> the bt_skb_cb struct rather than constantly doing shift and mask
>> operations.
>>
>> Signed-off-by: Mat Martineau<mathewm@codeaurora.org>
>> ---
>>   include/net/bluetooth/bluetooth.h |   14 ++-
>>   include/net/bluetooth/l2cap.h     |  260 +++++++++----------------------------
>>   2 files changed, 73 insertions(+), 201 deletions(-)
>
> <snip>
>
>> diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
>> index d6d8ec8..a499b60 100644
>> --- a/include/net/bluetooth/l2cap.h
>> +++ b/include/net/bluetooth/l2cap.h
>
> <snip>
>
>> @@ -645,200 +664,43 @@ static inline bool l2cap_clear_timer(struct l2cap_chan *chan,
>>
>>   #define __set_chan_timer(c, t) l2cap_set_timer(c,&c->chan_timer, (t))
>>   #define __clear_chan_timer(c) l2cap_clear_timer(c,&c->chan_timer)
>
> Are these two still needed? I saw you moved others to l2cap_core.c
> which is fine but what about these?

Since these macros are unrelated to ERTM, that would be a separate patch.

I think all the macros traditionally land in the header files because 
there are no #defines in the l2cap*.c files.  However, I see that many 
other .c files in net/bluetooth do have #defines.

It's not that I "moved" the other macros, as much as my ported code had 
static functions instead.  I tried to minimize changes to the ported 
code rather than minimize changes to the upstream code.

-- 
Mat Martineau
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum

  reply	other threads:[~2012-02-25  0:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 20:37 [RFC 0/2] New L2CAP ERTM state machine Mat Martineau
2012-02-23 20:37 ` [RFC 1/2] Bluetooth: Header changes for ERTM state machine replacement Mat Martineau
2012-02-24  9:48   ` Andrei Emeltchenko
2012-02-24 17:42     ` Ulisses Furquim
2012-02-25  0:21       ` Mat Martineau
2012-02-25 15:37         ` Ulisses Furquim
2012-02-27  9:28         ` Andrei Emeltchenko
2012-02-24 17:39   ` Ulisses Furquim
2012-02-25  0:32     ` Mat Martineau [this message]
2012-02-25 15:32       ` Ulisses Furquim
2012-02-28 23:33   ` Gustavo Padovan
2012-03-03  0:19     ` Mat Martineau
2012-02-23 20:37 ` [RFC 2/2] Bluetooth: L2CAP " Mat Martineau
2012-02-24 20:13   ` Ulisses Furquim
2012-02-25  1:08     ` Mat Martineau
2012-02-25 15:52       ` Ulisses Furquim
2012-02-27  9:15         ` Andrei Emeltchenko
2012-02-28 23:49       ` Gustavo Padovan
2012-03-03  0:30         ` Mat Martineau
2012-03-03  0:40           ` Marcel Holtmann
2012-03-06 23:09             ` Mat Martineau

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=4F482C0F.8000305@codeaurora.org \
    --to=mathewm@codeaurora.org \
    --cc=andrei.emeltchenko.news@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=padovan@profusion.mobi \
    --cc=pkrystad@codeaurora.org \
    --cc=ulisses@profusion.mobi \
    /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.