All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, florian@ubports.com
Subject: RE: plugins: Do not try to autopair with Nissan Connect devices
Date: Thu, 29 Sep 2022 14:30:03 -0700 (PDT)	[thread overview]
Message-ID: <63360e5b.a70a0220.a32de.0778@mx.google.com> (raw)
In-Reply-To: <01070182f561c630-852e0333-6f04-448b-b064-46a2f000e860-000000@eu-central-1.amazonses.com>

[-- Attachment #1: Type: text/plain, Size: 537 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: plugins/autopair.c:66
error: plugins/autopair.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


  parent reply	other threads:[~2022-09-29 21:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 19:30 [PATCH] plugins: Do not try to autopair with Nissan Connect devices Florian Leeber
2022-08-31 19:42 ` bluez.test.bot
2022-08-31 20:18 ` [PATCH] " Luiz Augusto von Dentz
2022-09-01 10:46   ` Bastien Nocera
2022-09-01 18:10     ` Florian Leeber
2022-09-01 23:56       ` Luiz Augusto von Dentz
2022-09-02 18:50         ` Florian Leeber
2022-09-29 16:49 ` bluez.test.bot
2022-09-29 17:44 ` bluez.test.bot
2022-09-29 18:40 ` bluez.test.bot
2022-09-29 19:01 ` bluez.test.bot
2022-09-29 19:29 ` bluez.test.bot
2022-09-29 19:47 ` bluez.test.bot
2022-09-29 20:34 ` bluez.test.bot
2022-09-29 20:53 ` bluez.test.bot
2022-09-29 21:30 ` bluez.test.bot [this message]
2022-09-29 21:52 ` bluez.test.bot
2022-09-29 22:32 ` bluez.test.bot
2022-09-29 22:52 ` bluez.test.bot
2022-09-29 23:40 ` bluez.test.bot
2022-09-29 23:59 ` 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=63360e5b.a70a0220.a32de.0778@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=florian@ubports.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.