All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/2] monitor: Check valid range of CE Length
Date: Thu, 10 Sep 2026 15:30:07 +0000	[thread overview]
Message-ID: <178905420738.1498636.178528734451251713.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260902150951.1583184-1-luiz.dentz@gmail.com>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed,  2 Sep 2026 11:09:50 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> The connection event length recommended in requests by a Peripheral has
> a valid range of 0x0001 to 0x7CFF (Time = N * 125 us, Time Range:
> 0.125 ms to 3.999875 s), so print values outside of it as reserved
> instead of decoding them as a time.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1,1/2] monitor: Check valid range of CE Length
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b93baad72d27
  - [BlueZ,v1,2/2] emulator/btdev: Check valid range of CE Length
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9d35770cb647

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-10 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 15:09 [PATCH BlueZ v1 1/2] monitor: Check valid range of CE Length Luiz Augusto von Dentz
2026-09-02 15:09 ` [PATCH BlueZ v1 2/2] emulator/btdev: " Luiz Augusto von Dentz
2026-09-02 18:09 ` [BlueZ,v1,1/2] monitor: " bluez.test.bot
2026-09-10 15:30 ` patchwork-bot+bluetooth [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=178905420738.1498636.178528734451251713.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.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 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.