Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v5 00/16] Functional/integration testing
Date: Thu, 14 May 2026 17:50:07 +0000	[thread overview]
Message-ID: <177878100755.31561.18184220318055008237.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1778688966.git.pav@iki.fi>

Hello:

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

On Wed, 13 May 2026 19:17:17 +0300 you wrote:
> Add framework for writing tests simulating "real" environments where
> BlueZ and other parts of the stack run on different virtual machine
> hosts that communicate with each other.
> 
> *** v5 ***
> 
> https://github.com/pv/bluez/compare/func-test-v4-r..func-test-v5
> 
> [...]

Here is the summary with links:
  - [BlueZ,v5,01/16] emulator: btvirt: check pkt lengths, don't get stuck on malformed
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e19c771841e9
  - [BlueZ,v5,02/16] emulator: btvirt: allow specifying where server unix sockets are made
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5ee43f9993dd
  - [BlueZ,v5,03/16] emulator: btvirt: support SCO data packets
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=cc077e4a12dd
  - [BlueZ,v5,04/16] emulator: btdev: clear more state on Reset
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f1a303e1d07a
  - [BlueZ,v5,05/16] test-runner: enable path argument for --unix
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ff2ecb82e4c3
  - [BlueZ,v5,06/16] test-runner: Add -o/--option option
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=82c635c879bf
  - [BlueZ,v5,07/16] test-runner: allow source tree root for -k
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1929b3a99d2f
  - [BlueZ,v5,08/16] test-runner: use virtio-serial for implementing -u device forwarding
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=908c14fc3abb
  - [BlueZ,v5,09/16] doc: enable CONFIG_VIRTIO_CONSOLE in tester config
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7856de4d69d6
  - [BlueZ,v5,10/16] doc: enable KVM paravirtualization & clock support in tester kernel config
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=48cb22a572c7
  - [BlueZ,v5,11/16] doc: add functional/integration testing documentation
    (no matching commit)
  - [BlueZ,v5,12/16] test: add functional/integration testing framework
    (no matching commit)
  - [BlueZ,v5,13/16] build: add functional testing target
    (no matching commit)
  - [BlueZ,v5,14/16] test: functional: impose Python code formatting
    (no matching commit)
  - [BlueZ,v5,15/16] test: functional: add some Agent1 interface tests
    (no matching commit)
  - [BlueZ,v5,16/16] test: functional: add basic obex file transfer tests
    (no matching commit)

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-05-14 17:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 16:17 [PATCH BlueZ v5 00/16] Functional/integration testing Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 01/16] emulator: btvirt: check pkt lengths, don't get stuck on malformed Pauli Virtanen
2026-05-13 18:23   ` Functional/integration testing bluez.test.bot
2026-05-13 16:17 ` [PATCH BlueZ v5 02/16] emulator: btvirt: allow specifying where server unix sockets are made Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 03/16] emulator: btvirt: support SCO data packets Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 04/16] emulator: btdev: clear more state on Reset Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 05/16] test-runner: enable path argument for --unix Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 06/16] test-runner: Add -o/--option option Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 07/16] test-runner: allow source tree root for -k Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 08/16] test-runner: use virtio-serial for implementing -u device forwarding Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 09/16] doc: enable CONFIG_VIRTIO_CONSOLE in tester config Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 10/16] doc: enable KVM paravirtualization & clock support in tester kernel config Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 11/16] doc: add functional/integration testing documentation Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 12/16] test: add functional/integration testing framework Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 13/16] build: add functional testing target Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 14/16] test: functional: impose Python code formatting Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 15/16] test: functional: add some Agent1 interface tests Pauli Virtanen
2026-05-13 16:17 ` [PATCH BlueZ v5 16/16] test: functional: add basic obex file transfer tests Pauli Virtanen
2026-05-14 17:50 ` patchwork-bot+bluetooth [this message]
2026-05-14 19:11   ` [PATCH BlueZ v5 00/16] Functional/integration testing Luiz Augusto von Dentz

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=177878100755.31561.18184220318055008237.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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