From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Daniel Winkler <danielwinkler@google.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
ChromeOS Bluetooth Upstreaming
<chromeos-bluetooth-upstreaming@chromium.org>
Subject: Re: [Bluez PATCH v4 0/3] Expose extended adv feature support via bluez API
Date: Wed, 17 Mar 2021 11:34:50 -0700 [thread overview]
Message-ID: <CABBYNZJ6Xvt_tAqST4EOz2z4Zom1kJ3goRfpPQ9BDwmBZf-iGw@mail.gmail.com> (raw)
In-Reply-To: <20210316232217.3344489-1-danielwinkler@google.com>
Hi Daniel,
On Tue, Mar 16, 2021 at 4:27 PM Daniel Winkler <danielwinkler@google.com> wrote:
>
> Hi Maintainers,
>
> I believe this series fell through the cracks. It is listed on
> patchworks as "Accepted", but I have not been able to find it in the
> tree. I am re-posting it here, please advise if I am mistaken.
>
> This change adds a SupportedFeatures member to the LEAdvertisingManager
> interface, which allows us to expose support for hardware offloading and
> setting TX power on advertisements.
>
> Best,
> Daniel
>
> Changes in v4:
> - Mark SupportedFeatures as experimental
>
> Changes in v3:
> - Rebased onto master
>
> Changes in v2:
> - Expose empty SupportedFeatures if no support available
> - Doc: Expect empty SupportedFeatures if no support available
>
> Daniel Winkler (3):
> advertising: Add SupportedFeatures to LEAdvertisingManager1
> client: Add adv SupportedFeatures to bluetoothctl
> doc/advertising-api: Add adv SupportedFeatures to doc
>
> client/main.c | 1 +
> doc/advertising-api.txt | 18 +++++++++++++++++
> lib/mgmt.h | 2 ++
> src/advertising.c | 44 +++++++++++++++++++++++++++++++++++++++--
> 4 files changed, 63 insertions(+), 2 deletions(-)
>
> --
> 2.31.0.rc2.261.g7f71774620-goog
Applied, thanks.
--
Luiz Augusto von Dentz
prev parent reply other threads:[~2021-03-17 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 23:22 [Bluez PATCH v4 0/3] Expose extended adv feature support via bluez API Daniel Winkler
2021-03-16 23:22 ` [Bluez PATCH v4 1/3] advertising: Add SupportedFeatures to LEAdvertisingManager1 Daniel Winkler
2021-03-16 23:37 ` Expose extended adv feature support via bluez API bluez.test.bot
2021-03-16 23:22 ` [Bluez PATCH v4 2/3] client: Add adv SupportedFeatures to bluetoothctl Daniel Winkler
2021-03-16 23:22 ` [Bluez PATCH v4 3/3] doc/advertising-api: Add adv SupportedFeatures to doc Daniel Winkler
2021-03-17 18:34 ` Luiz Augusto von Dentz [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=CABBYNZJ6Xvt_tAqST4EOz2z4Zom1kJ3goRfpPQ9BDwmBZf-iGw@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=danielwinkler@google.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.