From: patchwork-bot+bluetooth@kernel.org
To: Zhengping Jiang <jiangzp@google.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
chromeos-bluetooth-upstreaming@chromium.org, brian.gix@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
johan.hedberg@gmail.com, luiz.dentz@gmail.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [kernel PATCH v1 0/1] Fix refresh cached connection info
Date: Tue, 21 Jun 2022 19:30:13 +0000 [thread overview]
Message-ID: <165583981375.29669.2524383777560438152.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220613214327.15866-1-jiangzp@google.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 13 Jun 2022 14:43:26 -0700 you wrote:
> Get connection info will return error when using synchronous hci_sync
> call to refresh the cached information when the data times out. This is
> because the cmd->user_data was not set before the call, so it will fail
> checking connection is still connected.
>
> Changes in v1:
> - Set connection data before calling hci_cmd_sync_queue
>
> [...]
Here is the summary with links:
- [kernel,v1,1/1] Bluetooth: mgmt: Fix refresh cached connection info
https://git.kernel.org/bluetooth/bluetooth-next/c/d9cc9d78ca85
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-06-21 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 21:43 [kernel PATCH v1 0/1] Fix refresh cached connection info Zhengping Jiang
2022-06-13 21:43 ` [kernel PATCH v1 1/1] Bluetooth: mgmt: " Zhengping Jiang
2022-06-13 23:04 ` bluez.test.bot
2022-06-21 19:30 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-10 19:19 [kernel PATCH v1 0/1] " Zhengping Jiang
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=165583981375.29669.2524383777560438152.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brian.gix@intel.com \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiangzp@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).