From: "Guðni Már Gilbert" <gudni.m.g@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bluez5: upgrade 5.85 -> 5.86
Date: Sat, 14 Feb 2026 07:34:30 -0800 [thread overview]
Message-ID: <1493339.1771083270694896639@lists.openembedded.org> (raw)
In-Reply-To: <20260214153039.2022198-1-gudni.m.g@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
Note I am not the maintainer of this recipe and I just want to see BlueZ being up to date, especially before new LTS :)
I ran the ptests locally and all of them passed. I did not verify if BlueZ 5.86 builds with musl.
Below are the steps I used to test:
1) run: bitbake core-image-ptest-bluez5
2) run: runqemu qemux86-64 core-image-ptest-bluez5 slirp nographic snapshot
3) run: /usr/lib/bluez5/ptest/ptest-runner bluez5
[-- Attachment #2: Type: text/html, Size: 530 bytes --]
next prev parent reply other threads:[~2026-02-14 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 15:30 [PATCH] bluez5: upgrade 5.85 -> 5.86 Guðni Már Gilbert
2026-02-14 15:34 ` Guðni Már Gilbert [this message]
2026-02-15 11:11 ` Guðni Már Gilbert
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=1493339.1771083270694896639@lists.openembedded.org \
--to=gudni.m.g@gmail.com \
--cc=openembedded-core@lists.openembedded.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