All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: Re: [PATCH BlueZ v2] adapter: Use regular discovery for filters which only have discoverable set
Date: Fri, 31 Mar 2023 22:20:18 +0000	[thread overview]
Message-ID: <168030121898.14188.14830989349670597911.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230331200329.461355-1-hdegoede@redhat.com>

Hello:

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

On Fri, 31 Mar 2023 22:03:29 +0200 you wrote:
> discovery_filter_to_mgmt_cp() does not add discovery_filter.discoverable
> to the created mgmt_cp_start_service_discovery struct.
> 
> Instead update_discovery_filter() separately checks
> client->discovery_filter->discoverable for all clients.
> 
> This means that for discovery-filters which only have the discoverable
> flag set, to put the adapter in discoverable mode while discovering,
> the created mgmt_cp_start_service_discovery struct is empty.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2] adapter: Use regular discovery for filters which only have discoverable set
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=de8e7cfce25b

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



      parent reply	other threads:[~2023-03-31 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 20:03 [PATCH BlueZ v2] adapter: Use regular discovery for filters which only have discoverable set Hans de Goede
2023-03-31 21:17 ` [BlueZ,v2] " bluez.test.bot
2023-03-31 22:20 ` 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=168030121898.14188.14830989349670597911.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=hadess@hadess.net \
    --cc=hdegoede@redhat.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.