All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: wangyouwan <wangyouwan@uniontech.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] device: Fix pairing has failed due to the error of Already Paired (0x13)
Date: Wed, 11 May 2022 21:40:12 +0000	[thread overview]
Message-ID: <165230521242.17601.4484740268374199473.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220510012735.1698-1-wangyouwan@uniontech.com>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 10 May 2022 09:27:35 +0800 you wrote:
> After connect the Bluetooth mouse, open two Bluetoothctl at the same time,
> when remove the mouse, quickly go to power off,
> try to paired the mouse again when I was power on,
> found that the error 0x13 was always reported.
> try to connect directly,can connect successfully.
> but use the info command to query the information of the mouse
> and find that the pairing status of the mouse is No.
> so I try to delete the paired information in the kernel
> through the "* cancel_pairing()" interface.
> 
> [...]

Here is the summary with links:
  - device: Fix pairing has failed due to the error of Already Paired (0x13)
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4423d63a9634

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-05-11 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  1:27 [PATCH] device: Fix pairing has failed due to the error of Already Paired (0x13) wangyouwan
2022-05-10  3:01 ` bluez.test.bot
2022-05-11 21:40 ` patchwork-bot+bluetooth [this message]

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=165230521242.17601.4484740268374199473.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=wangyouwan@uniontech.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 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.