All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Sarmanow <as@discnull.de>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/2] org.bluez.LEAdvertisement: Add broadcast name support
Date: Thu, 24 Sep 2026 20:57:20 +0200	[thread overview]
Message-ID: <arVykKJmqbhL0pEo@machine> (raw)
In-Reply-To: <CABBYNZJhvRubX7w7Wj6cKMPvSUFr-GsnqYBYJp66sWGW153Y6w@mail.gmail.com>

Hi Luiz,

thank you for your quick reply.

> This is already supported on bluetoothctl; see:

I was aware of the blutoothctl implementation, but my motiviation came
from pipewire where to my knowledge no such mechanism is existing yet
and thought it would be nice to shift it to bluetoothd. However I
understand your perspective of what's the role of the client!

> Now it doesn't seem to have the string limits you pointed out, so
> perhaps it is worth extending it. We could, in theory move the
> detection of the PBP uuid to bluetoothd

I will take a look on both the extension of the string limits and moving
the PBP UUID detection to the daemon.

Thanks for your time.

Best,
Alexander

      reply	other threads:[~2026-09-24 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 15:17 [PATCH BlueZ 0/2] org.bluez.LEAdvertisement: Add broadcast name support Alexander Sarmanow
2026-09-24 15:17 ` [PATCH BlueZ 1/2] doc/org.bluez.LEAdvertisement: Add broadcast name Alexander Sarmanow
2026-09-24 19:06   ` org.bluez.LEAdvertisement: Add broadcast name support bluez.test.bot
2026-10-09 19:52   ` bluez.test.bot
2026-09-24 15:17 ` [PATCH BlueZ 2/2] advertising: Add broadcast name property support Alexander Sarmanow
2026-09-24 15:44 ` [PATCH BlueZ 0/2] org.bluez.LEAdvertisement: Add broadcast name support Luiz Augusto von Dentz
2026-09-24 18:57   ` Alexander Sarmanow [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=arVykKJmqbhL0pEo@machine \
    --to=as@discnull.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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.