From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] test-runner: set non-quiet printk before running tests
Date: Thu, 13 Jul 2023 19:26:57 +0000 [thread overview]
Message-ID: <168927641746.6361.8863203110548738608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <e521a8d35e8baff45db1fdf8a26725bdc8d595ee.1689196901.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 Thu, 13 Jul 2023 00:22:48 +0300 you wrote:
> It is useful to see WARN_ON etc. messages when running the tests.
>
> The 'quiet' in cmdline suppresses levels >= WARN, so re-enable them
> explicitly after boot, so that it is on by default and doesn't need to
> be handled in local test scripts.
> ---
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] test-runner: set non-quiet printk before running tests
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7cea6b964119
- [BlueZ,v2,2/2] test-runner: fix behavior when no audio server
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9aff3f494142
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:[~2023-07-13 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 21:22 [PATCH BlueZ v2 1/2] test-runner: set non-quiet printk before running tests Pauli Virtanen
2023-07-12 21:22 ` [PATCH BlueZ v2 2/2] test-runner: fix behavior when no audio server Pauli Virtanen
2023-07-12 22:44 ` [BlueZ,v2,1/2] test-runner: set non-quiet printk before running tests bluez.test.bot
2023-07-13 19:26 ` 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=168927641746.6361.8863203110548738608.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.