From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: test-runner: Add support for audio daemons
Date: Thu, 09 Jun 2022 12:21:31 -0700 (PDT) [thread overview]
Message-ID: <62a2483b.1c69fb81.4646b.9b6f@mx.google.com> (raw)
In-Reply-To: <20220609190442.74325-2-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
This is an automated email and please do not reply to this email.
Dear Submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
While preparing the CI tests, the patches you submitted couldn't be applied to the current HEAD of the repository.
----- Output -----
error: patch failed: tools/test-runner.c:445
error: tools/test-runner.c: patch does not apply
hint: Use 'git am --show-current-patch' to see the failed patch
Please resolve the issue and submit the patches again.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-09 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 19:04 [PATCH 0/3] test-runner: Add support for audio daemons Frédéric Danis
2022-06-09 19:04 ` [PATCH 1/3] test-runner: Add DBus session support Frédéric Danis
2022-06-09 19:21 ` bluez.test.bot [this message]
2022-06-09 19:04 ` [PATCH 2/3] test-runner: Add audio card support Frédéric Danis
2022-06-09 19:04 ` [PATCH 3/3] test-runner: Add udevd and trigger events Frédéric Danis
2022-06-10 3:41 ` [PATCH 0/3] test-runner: Add support for audio daemons Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2022-06-10 7:28 [PATCH BlueZ v2 1/3] test-runner: Add DBus session support Frédéric Danis
2022-06-10 9:51 ` test-runner: Add support for audio daemons bluez.test.bot
2022-06-10 16:38 [PATCH BlueZ v3 1/4] test-runner: Add DBus session support Frédéric Danis
2022-06-10 20:08 ` test-runner: Add support for audio daemons bluez.test.bot
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=62a2483b.1c69fb81.4646b.9b6f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.com \
--cc=linux-bluetooth@vger.kernel.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 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.