All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Matthew Cash <matthew@matthew-cash.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] profiles/midi: Fix zero timestampHigh
Date: Tue, 30 Jun 2026 20:32:47 +0000	[thread overview]
Message-ID: <178285156713.267316.12619611811577977707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260627224444.531788-1-matthew@matthew-cash.com>

Hello:

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

On Sat, 27 Jun 2026 15:44:44 -0700 you wrote:
> BLE-MIDI timestampHigh can legitimately be zero. The MIDI parser used
> timestamp_high == 0 to decide whether it had already consumed the packet
> header, so packets starting with 0x80 0x80 caused the next running-status
> payload byte to be consumed as another timestamp header.
> 
> Track whether timestampHigh has been read separately from its value so
> packed MIDI events with zero timestampHigh are parsed correctly.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2] profiles/midi: Fix zero timestampHigh
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=220f102c8db9

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-06-30 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 22:44 [PATCH BlueZ v2] profiles/midi: Fix zero timestampHigh Matthew Cash
2026-06-28  0:30 ` [BlueZ,v2] " bluez.test.bot
2026-06-30 20:32 ` 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=178285156713.267316.12619611811577977707.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=matthew@matthew-cash.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.