From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, max.oss.09@gmail.com
Subject: RE: [v1] Revert "Bluetooth: core: Fix missing power_on work cancel on HCI close"
Date: Tue, 14 Jun 2022 11:53:23 -0700 (PDT) [thread overview]
Message-ID: <62a8d923.1c69fb81.7be7c.e3a9@mx.google.com> (raw)
In-Reply-To: <20220614181706.26513-1-max.oss.09@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 551 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: net/bluetooth/hci_core.c:2675
error: net/bluetooth/hci_core.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-14 19:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 18:17 [PATCH v1] Revert "Bluetooth: core: Fix missing power_on work cancel on HCI close" Max Krummenacher
2022-06-14 18:53 ` bluez.test.bot [this message]
2022-06-21 11:55 ` Francesco Dolcini
2022-06-23 19:51 ` Jakub Kicinski
2022-07-04 19:56 ` Mateusz Jończyk
2022-07-05 14:09 ` Max Krummenacher
2022-07-05 12:59 ` [PATCH] Bluetooth: core: Fix deadlock due to `cancel_work_sync(&hdev->power_on)` from hci_power_on_sync Vasyl Vavrychuk
2022-07-05 14:12 ` Max Krummenacher
2022-07-05 14:13 ` bluez.test.bot
2022-07-05 15:14 ` [PATCH] " Francesco Dolcini
2022-07-05 17:26 ` Luiz Augusto von Dentz
2022-07-05 18:38 ` Jakub Kicinski
2022-07-05 19:00 ` Luiz Augusto von Dentz
2022-07-05 19:13 ` Jakub Kicinski
2022-07-05 18:38 ` Mateusz Jończyk
2022-07-05 21:50 ` patchwork-bot+netdevbpf
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=62a8d923.1c69fb81.7be7c.e3a9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=max.oss.09@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).