linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 3/3] Bluetooth: Auto tune if input MTU is set to 0
Date: Sat, 4 Jan 2020 10:52:44 +0100	[thread overview]
Message-ID: <CBD1124A-0C1D-499E-88F5-5E9993000AE1@holtmann.org> (raw)
In-Reply-To: <20200102230057.31326-3-luiz.dentz@gmail.com>

Hi Luiz,

> This enables the code to set the input MTU using the underline link
> packet types when set to 0, previously this would likely be rejected by
> the remote peer since it would be bellow the minimal of 48 for BR/EDR
> or 23 for LE, that way it shall be safe to use 0 without causing any
> side effects.
> 
> This is convenient for the likes of A2DP transport, see:
> 
> https://habr.com/en/post/456182/
> 
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> ---
> net/bluetooth/l2cap_core.c | 54 ++++++++++++++++++++++++++++++++++++--
> 1 file changed, 52 insertions(+), 2 deletions(-)

patch has been applied to bluetooth-next tree.

Regards

Marcel


  reply	other threads:[~2020-01-04  9:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 23:00 [RFC 1/3] Bluetooth: HCI: Add support for LE PHY Update Complete event Luiz Augusto von Dentz
2020-01-02 23:00 ` [RFC 2/3] Bluetooth: Add BT_PHYS socket option Luiz Augusto von Dentz
2020-01-04  9:55   ` Marcel Holtmann
2020-01-07 22:04     ` Luiz Augusto von Dentz
2020-01-08 20:52       ` Marcel Holtmann
2020-01-08 21:08         ` Luiz Augusto von Dentz
2020-01-02 23:00 ` [RFC 3/3] Bluetooth: Auto tune if input MTU is set to 0 Luiz Augusto von Dentz
2020-01-04  9:52   ` Marcel Holtmann [this message]
2020-01-04  9:50 ` [RFC 1/3] Bluetooth: HCI: Add support for LE PHY Update Complete event Marcel Holtmann

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=CBD1124A-0C1D-499E-88F5-5E9993000AE1@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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).