All of lore.kernel.org
 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 v7 0/9] Functional/integration testing
Date: Tue, 08 Sep 2026 19:20:09 +0000	[thread overview]
Message-ID: <178889520963.3704993.9911217550470009790.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1788712996.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 Sun,  6 Sep 2026 19:49:42 +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.
> 
> *** v7 ***
> 
> * Bump to pytest-bluezenv==0.1.9 (better core dump / oops reporting)
> 
> [...]

Here is the summary with links:
  - [BlueZ,v7,1/9] doc: add functional/integration testing documentation
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=19a5bbd7eee2
  - [BlueZ,v7,2/9] test: add functional/integration testing framework
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fa9390b5cee3
  - [BlueZ,v7,3/9] build: add functional testing target
    (no matching commit)
  - [BlueZ,v7,4/9] test: functional: impose Python code formatting
    (no matching commit)
  - [BlueZ,v7,5/9] test: functional: add some Agent1 interface tests
    (no matching commit)
  - [BlueZ,v7,6/9] test: functional: add basic obex file transfer tests
    (no matching commit)
  - [BlueZ,v7,7/9] test: functional: add tests running the various kernel testers
    (no matching commit)
  - [BlueZ,v7,8/9] test: functional: add test for adv_monitor crash
    (no matching commit)
  - [BlueZ,v7,9/9] test: functional: add test for AVRCP crash
    (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-09-08 19:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06 16:49 [PATCH BlueZ v7 0/9] Functional/integration testing Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 1/9] doc: add functional/integration testing documentation Pauli Virtanen
2026-09-06 18:29   ` Functional/integration testing bluez.test.bot
2026-09-06 16:49 ` [PATCH BlueZ v7 2/9] test: add functional/integration testing framework Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 3/9] build: add functional testing target Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 4/9] test: functional: impose Python code formatting Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 5/9] test: functional: add some Agent1 interface tests Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 6/9] test: functional: add basic obex file transfer tests Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 7/9] test: functional: add tests running the various kernel testers Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 8/9] test: functional: add test for adv_monitor crash Pauli Virtanen
2026-09-06 16:49 ` [PATCH BlueZ v7 9/9] test: functional: add test for AVRCP crash Pauli Virtanen
2026-09-08 17:48 ` [PATCH BlueZ v7 0/9] Functional/integration testing Luiz Augusto von Dentz
2026-09-08 18:33   ` Pauli Virtanen
2026-09-08 19:20 ` patchwork-bot+bluetooth [this message]
2026-09-09 18:56   ` Luiz Augusto von Dentz
2026-09-10 17:47     ` Luiz Augusto von Dentz
2026-09-11 16:08       ` Pauli Virtanen
2026-09-11 16:31         ` Luiz Augusto von Dentz
2026-09-11 17:04           ` Pauli Virtanen
2026-09-08 20:00 ` patchwork-bot+bluetooth

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=178889520963.3704993.9911217550470009790.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 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.