From: patchwork-bot+bluetooth@kernel.org
To: Simon Mikuda <simon.mikuda@streamunlimited.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v3 1/3] device: Refactor device_discover_services function
Date: Mon, 08 Jun 2026 18:20:05 +0000 [thread overview]
Message-ID: <178094280590.1611786.9656752932765017197.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260608110743.3683728-1-simon.mikuda@streamunlimited.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 8 Jun 2026 13:07:41 +0200 you wrote:
> After refactoring we can reuse function once more in function
> void device_bonding_complete(...)
> ---
> profiles/input/server.c | 2 +-
> src/adapter.c | 2 +-
> src/device.c | 26 ++++++++------------------
> src/device.h | 3 ++-
> 4 files changed, 12 insertions(+), 21 deletions(-)
Here is the summary with links:
- [BlueZ,v3,1/3] device: Refactor device_discover_services function
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=56835e9061de
- [BlueZ,v3,2/3] device: Rename start_discovery function
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=415955bb70ba
- [BlueZ,v3,3/3] device: Fix returning discovery error for Device.Pair
(no matching commit)
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:[~2026-06-08 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 10:39 [PATCH BlueZ 1/3] device: Refactor device_discover_services function Simon Mikuda
2026-06-08 10:39 ` [PATCH BlueZ 2/3] device: Rename start_discovery function Simon Mikuda
2026-06-08 10:39 ` [PATCH BlueZ 3/3] device: Fix returning discovery error for Device.Pair Simon Mikuda
2026-06-08 10:59 ` [PATCH BlueZ v2 1/3] device: Refactor device_discover_services function Simon Mikuda
2026-06-08 10:59 ` [PATCH BlueZ v2 2/3] device: Rename start_discovery function Simon Mikuda
2026-06-08 10:59 ` [PATCH BlueZ v2 3/3] device: Fix returning discovery error for Device.Pair Simon Mikuda
2026-06-08 11:41 ` [BlueZ,v2,1/3] device: Refactor device_discover_services function bluez.test.bot
2026-06-08 11:07 ` [PATCH BlueZ v3 1/3] " Simon Mikuda
2026-06-08 11:07 ` [PATCH BlueZ v3 2/3] device: Rename start_discovery function Simon Mikuda
2026-06-08 11:07 ` [PATCH BlueZ v3 3/3] device: Fix returning discovery error for Device.Pair Simon Mikuda
2026-06-08 12:25 ` [BlueZ,v3,1/3] device: Refactor device_discover_services function bluez.test.bot
2026-06-08 18:20 ` patchwork-bot+bluetooth [this message]
2026-06-08 11:40 ` [BlueZ,1/3] " 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=178094280590.1611786.9656752932765017197.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon.mikuda@streamunlimited.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