From: joeyli <jlee@suse.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Bluetooth: ignore NULL link key and reject connection
Date: Sun, 1 Oct 2023 16:39:19 +0800 [thread overview]
Message-ID: <20231001083919.GD8209@linux-l9pv.suse> (raw)
In-Reply-To: <65192a7a.050a0220.74207.ee6c@mx.google.com>
Hi experts,
hm... I will port my patch to newest mainline kernel and send out series again.
Sorry for any inconvenience caused!
Joey Lee
On Sun, Oct 01, 2023 at 01:14:50AM -0700, bluez.test.bot@gmail.com wrote:
> 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_event.c:4692
> error: net/bluetooth/hci_event.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-10-01 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 7:45 [PATCH 0/2] Bluetooth: ignore NULL link key and reject connection Lee, Chun-Yi
2023-10-01 7:48 ` [PATCH 1/2] Bluetooth: hci_event: Ignore NULL link key Lee, Chun-Yi
2023-10-01 8:14 ` Bluetooth: ignore NULL link key and reject connection bluez.test.bot
2023-10-01 8:39 ` joeyli [this message]
2023-10-01 7:48 ` [PATCH 2/2] Bluetooth: Reject connection with the device which has same BD_ADDR Lee, Chun-Yi
2023-10-01 8:05 ` [PATCH 0/2] Bluetooth: ignore NULL link key and reject connection joeyli
2023-10-01 8:08 ` [PATCH 1/2] Bluetooth: hci_event: Ignore NULL link key Lee, Chun-Yi
2023-10-01 8:44 ` [1/2] " bluez.test.bot
2023-10-01 8:09 ` [PATCH 2/2] Bluetooth: Reject connection with the device which has same BD_ADDR Lee, Chun-Yi
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=20231001083919.GD8209@linux-l9pv.suse \
--to=jlee@suse.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.