From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: hci_sync req_complete_skb does not get called?
Date: Sun, 21 May 2023 09:37:47 -0700 (PDT) [thread overview]
Message-ID: <646a48db.9d0a0220.aba4c.5518@mx.google.com> (raw)
In-Reply-To: <6f0674a4bafc17ab4ab34b0fec99f9e4a1312a90.1684684404.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 539 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/iso-tester.c:2303
error: tools/iso-tester.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:[~2023-05-21 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 15:27 [PATCH BlueZ 1/5] iso-tester: always use DEFER_SETUP for multiple CIS in same CIG Pauli Virtanen
2023-05-21 15:27 ` [PATCH BlueZ 2/5] shared/tester: retain test failure status Pauli Virtanen
2023-05-21 15:27 ` [PATCH BlueZ 3/5] btdev: support multiple CIG Pauli Virtanen
2023-05-21 15:27 ` [PATCH BlueZ 4/5] btdev: report right reason for local Disconnect complete Pauli Virtanen
2023-05-21 15:27 ` [PATCH BlueZ 5/5] iso-tester: add tests for multiple simultaneous CIG Pauli Virtanen
2023-05-22 18:28 ` Luiz Augusto von Dentz
2023-05-22 20:38 ` Pauli Virtanen
2023-05-22 20:48 ` Luiz Augusto von Dentz
2023-05-22 23:08 ` Luiz Augusto von Dentz
2023-05-21 16:15 ` hci_sync req_complete_skb does not get called? Pauli Virtanen
2023-05-21 16:37 ` bluez.test.bot [this message]
2023-05-21 18:11 ` [BlueZ,1/5] iso-tester: always use DEFER_SETUP for multiple CIS in same CIG bluez.test.bot
2023-05-22 20:20 ` [PATCH BlueZ 1/5] " patchwork-bot+bluetooth
2023-05-22 20:27 ` 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=646a48db.9d0a0220.aba4c.5518@mx.google.com \
--to=bluez.test.bot@gmail.com \
--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