From: Mat Martineau <mathewm@codeaurora.org>
To: linux-bluetooth@vger.kernel.org
Cc: gustavo@padovan.org, pkrystad@codeaurora.org,
marcel@holtmann.org, andrei.emeltchenko.news@gmail.com,
szymon.janc@tieto.com, Mat Martineau <mathewm@codeaurora.org>
Subject: [PATCHv4 0/2] ERTM state machine changes, part 1
Date: Wed, 4 Apr 2012 11:29:41 -0700 [thread overview]
Message-ID: <1333564183-23442-1-git-send-email-mathewm@codeaurora.org> (raw)
This is the first of several patch series to rework the ERTM state
machine.
PATCHv1: Four patches, two patches updating header files were merged
PATCHv2: Reworked utility functions for seq_lists and control headers.
PATCHv3: Removed extra debug output, added error handling for
allocation failure, used some long lines at Marcel's request, removed
an unnecessary variable, and added a __set_control function.
PATCHv4: Use roundup_pow_of_two macro and kmalloc
Mat Martineau (2):
Bluetooth: Add the l2cap_seq_list structure for tracking frames
(Acked-by Marcel at v2, but added new error handling code in v3)
Bluetooth: Functions for handling ERTM control fields
include/net/bluetooth/l2cap.h | 12 ++
net/bluetooth/l2cap_core.c | 247 +++++++++++++++++++++++++++++++++++++++--
2 files changed, 251 insertions(+), 8 deletions(-)
--
1.7.9.4
--
Mat Martineau
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next reply other threads:[~2012-04-04 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 18:29 Mat Martineau [this message]
2012-04-04 18:29 ` [PATCHv4 1/2] Bluetooth: Add the l2cap_seq_list structure for tracking frames Mat Martineau
2012-04-04 20:30 ` Marcel Holtmann
2012-04-04 18:29 ` [PATCHv4 2/2] Bluetooth: Functions for handling ERTM control fields Mat Martineau
2012-04-04 20:31 ` Marcel Holtmann
2012-04-06 14:48 ` Mat Martineau
2012-04-06 22:29 ` Gustavo Padovan
2012-04-06 22:36 ` Gustavo Padovan
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=1333564183-23442-1-git-send-email-mathewm@codeaurora.org \
--to=mathewm@codeaurora.org \
--cc=andrei.emeltchenko.news@gmail.com \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pkrystad@codeaurora.org \
--cc=szymon.janc@tieto.com \
/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).