From: Gustavo Padovan <gustavo@padovan.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv1 7/7] Bluetooth: Adjust L2CAP Max PDU size for AMP packets
Date: Mon, 8 Oct 2012 06:25:00 +0800 [thread overview]
Message-ID: <20121007222500.GC13325@joana> (raw)
In-Reply-To: <1349445419-16788-7-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
* Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com> [2012-10-05 16:56:58 +0300]:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> Maximum PDU size is defined by new BT Spec as 1492 octets.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> include/net/bluetooth/l2cap.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Patches 2 to 7 were applied to bluetooth-next. Thanks.
Gustavo
next prev parent reply other threads:[~2012-10-07 22:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 13:56 [PATCHv1 1/7] Bluetooth: L2CAP: Fix using default Flush Timeout for EFS Andrei Emeltchenko
2012-10-05 13:56 ` [PATCHv1 2/7] Bluetooth: AMP: Fix possible NULL dereference Andrei Emeltchenko
2012-10-05 13:56 ` [PATCHv1 3/7] Bluetooth: Fix dereference after NULL check Andrei Emeltchenko
2012-10-05 13:56 ` [PATCHv1 4/7] Bluetooth: AMP: Factor out amp_ctrl_add Andrei Emeltchenko
2012-10-05 13:56 ` [PATCHv1 5/7] Bluetooth: AMP: Factor out phylink_add Andrei Emeltchenko
2012-10-05 13:56 ` [PATCHv1 6/7] Bluetooth: AMP: Use block_mtu for AMP controller Andrei Emeltchenko
2012-10-05 13:56 ` [PATCHv1 7/7] Bluetooth: Adjust L2CAP Max PDU size for AMP packets Andrei Emeltchenko
2012-10-05 17:40 ` Mat Martineau
2012-10-07 22:25 ` Gustavo Padovan [this message]
2012-10-07 21:48 ` [PATCHv1 1/7] Bluetooth: L2CAP: Fix using default Flush Timeout for EFS Gustavo Padovan
2012-10-08 8:14 ` [PATCH] " Andrei Emeltchenko
2012-10-08 12:41 ` 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=20121007222500.GC13325@joana \
--to=gustavo@padovan.org \
--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).