From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Mat Martineau <mathewm@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
gustavo@padovan.org, rshaffer@codeaurora.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/5] Bluetooth: Only enable for L2CAP FCS for ERTM or streaming
Date: Wed, 25 Aug 2010 14:11:16 -0300 [thread overview]
Message-ID: <20100825171116.GA13872@vigoh> (raw)
In-Reply-To: <1282689346-20371-2-git-send-email-mathewm@codeaurora.org>
Hi Mat,
* Mat Martineau <mathewm@codeaurora.org> [2010-08-24 15:35:42 -0700]:
> This fixes a bug which caused the FCS setting to show L2CAP_FCS_CRC16
> with L2CAP modes other than ERTM or streaming. At present, this only
> affects the FCS value shown with getsockopt() for basic mode.
>
> Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
> ---
> net/bluetooth/l2cap.c | 19 +++++++++++++------
> 1 files changed, 13 insertions(+), 6 deletions(-)
This one is on bluetooth-testing, but Marcel should move it to
bluetooth-2.6 as this patch is planned to go into 2.6.36
--
Gustavo F. Padovan
ProFUSION embedded systems - http://profusion.mobi
next prev parent reply other threads:[~2010-08-25 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 22:35 [PATCH v5 0/5] L2CAP updates for FCS, valid PSMs, and stream recv Mat Martineau
2010-08-24 22:35 ` [PATCH 1/5] Bluetooth: Only enable for L2CAP FCS for ERTM or streaming Mat Martineau
2010-08-25 17:11 ` Gustavo F. Padovan [this message]
2010-08-24 22:35 ` [PATCH 2/5] Bluetooth: Validate PSM values in calls to connect() and bind() Mat Martineau
2010-09-02 23:53 ` Mat Martineau
2010-08-24 22:35 ` [PATCH 3/5] Bluetooth: Add common code for stream-oriented recvmsg() Mat Martineau
2010-08-24 22:35 ` [PATCH 4/5] Bluetooth: Use common SOCK_STREAM receive code in RFCOMM Mat Martineau
2010-08-24 22:35 ` [PATCH 5/5] Bluetooth: Use a stream-oriented recvmsg with SOCK_STREAM L2CAP sockets 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=20100825171116.GA13872@vigoh \
--to=padovan@profusion.mobi \
--cc=gustavo@padovan.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mathewm@codeaurora.org \
--cc=rshaffer@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 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.