From: Marcel Holtmann <marcel@holtmann.org>
To: Mat Martineau <mathewm@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org, gustavo@padovan.org,
pkrystad@codeaurora.org
Subject: Re: [PATCHv6 0/2] ERTM state machine changes, part 1
Date: Thu, 12 Apr 2012 22:38:56 +0200 [thread overview]
Message-ID: <1334263136.16897.145.camel@aeonflux> (raw)
In-Reply-To: <1334166523-11060-1-git-send-email-mathewm@codeaurora.org>
Hi Mat,
> 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
> PATCHv5: No warnings
> PATCHv6: Fix indentation issue introduced in v5
>
> Mat Martineau (2):
> Bluetooth: Add the l2cap_seq_list structure for tracking frames
> Bluetooth: Functions for handling ERTM control fields
>
> include/net/bluetooth/l2cap.h | 12 ++
> net/bluetooth/l2cap_core.c | 263 +++++++++++++++++++++++++++++++++++++++--
> 2 files changed, 267 insertions(+), 8 deletions(-)
I have no idea why neither Gustavo nor Johan applied these patches. So I
just went ahead and pushed them into bluetooth-next tree.
Regards
Marcel
prev parent reply other threads:[~2012-04-12 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 17:48 [PATCHv6 0/2] ERTM state machine changes, part 1 Mat Martineau
2012-04-11 17:48 ` [PATCHv6 1/2] Bluetooth: Add the l2cap_seq_list structure for tracking frames Mat Martineau
2012-04-11 17:48 ` [PATCHv6 2/2] Bluetooth: Functions for handling ERTM control fields Mat Martineau
2012-04-12 20:38 ` Marcel Holtmann [this message]
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=1334263136.16897.145.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mathewm@codeaurora.org \
--cc=pkrystad@codeaurora.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