From: Gustavo Padovan <padovan@profusion.mobi>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv3 3/6] Bluetooth: EFS: add efs option in L2CAP conf req
Date: Thu, 13 Oct 2011 17:10:25 -0300 [thread overview]
Message-ID: <20111013201025.GE20892@joana> (raw)
In-Reply-To: <1318511938-24311-4-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
* Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com> [2011-10-13 16:18:55 +0300]:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> Add Extended Flow Specification option when building L2CAP
> Configuration Request. EFS is added if both the local and
> remote L2CAP entities have indicated support for the
> Extended Flow Specification for BR/EDR.
>
> ...
> < ACL data: handle 1 flags 0x00 dlen 10
> L2CAP(s): Info req: type 2
> > ACL data: handle 1 flags 0x02 dlen 16
> L2CAP(s): Info rsp: type 2 result 0
> Extended feature mask 0x01f8
> Enhanced Retransmission mode
> Streaming mode
> FCS Option
> Extended Flow Specification
> Fixed Channels
> Extended Window Size
> ...
> < ACL data: handle 1 flags 0x00 dlen 45
> L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 33
> RFC 0x03 (Enhanced Retransmission, TxWin 63, MaxTx 3, RTo 0, MTo 0, MPS 498)
> EFS (Id 0x01, SerType Best Effort, MaxSDU 0xffff, SDUitime 0xffffffff,
> AccLat 0xffffffff, FlushTO 0x0000ffff)
> ...
>
> Based upon haijun.liu <haijun.liu@atheros.com> series of patches
> (sent Sun, 22 Aug 2010)
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> net/bluetooth/l2cap_core.c | 45 ++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 45 insertions(+), 0 deletions(-)
Patches 1 to 3 have been applied. Thanks.
Gustavo
next prev parent reply other threads:[~2011-10-13 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 13:18 [PATCHv3 0/6] EFS: extended flow specification option support Emeltchenko Andrei
2011-10-13 13:18 ` [PATCHv3 1/6] Bluetooth: EFS: definitions and headers Emeltchenko Andrei
2011-10-13 13:18 ` [PATCHv3 2/6] Bluetooth: EFS: assign default values in chan add Emeltchenko Andrei
2011-10-13 13:18 ` [PATCHv3 3/6] Bluetooth: EFS: add efs option in L2CAP conf req Emeltchenko Andrei
2011-10-13 20:10 ` Gustavo Padovan [this message]
2011-10-13 13:18 ` [PATCHv3 4/6] Bluetooth: EFS: parse L2CAP config request Emeltchenko Andrei
2011-10-13 20:15 ` Gustavo Padovan
2011-10-13 13:18 ` [PATCHv3 5/6] Bluetooth: EFS: parse L2CAP config response Emeltchenko Andrei
2011-10-13 13:18 ` [PATCHv3 6/6] Bluetooth: EFS: implement L2CAP config pending state 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=20111013201025.GE20892@joana \
--to=padovan@profusion.mobi \
--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 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).