From: patchwork-bot+bluetooth@kernel.org
To: RasmusML <rasmusml0501@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, rasmusml@hotmail.dk
Subject: Re: [PATCH BlueZ 1/2] profiles/midi: Fix running status across channels
Date: Tue, 03 Nov 2026 16:30:14 +0000 [thread overview]
Message-ID: <179372341454.1736455.18207620929462425550.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261102221223.16079-1-rasmusml0501@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 2 Nov 2026 23:12:22 +0100 you wrote:
> From: RasmusML <rasmusml@hotmail.dk>
>
> When two MIDI messages of the same type but on different channels end
> up in the same BLE-MIDI packet, read_ev_others() writes the second
> status byte without the timestampLow byte that must precede every
> status byte. A receiver then reads that status byte as the timestamp
> and applies the following data bytes to the previous message's channel
> through running status, e.g.:
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] profiles/midi: Fix running status across channels
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=737e84da251a
- [BlueZ,2/2] unit/test-midi: Add multi-channel writer test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ae27e4a2baf4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-03 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 22:12 [PATCH BlueZ 1/2] profiles/midi: Fix running status across channels RasmusML
2026-11-02 22:12 ` [PATCH BlueZ 2/2] unit/test-midi: Add multi-channel writer test RasmusML
2026-11-03 1:57 ` [BlueZ,1/2] profiles/midi: Fix running status across channels bluez.test.bot
2026-11-03 16: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=179372341454.1736455.18207620929462425550.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=rasmusml0501@gmail.com \
--cc=rasmusml@hotmail.dk \
/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