From: Sonny Sasaka <sonnysasaka@chromium.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [BlueZ,v5,1/7] battery: Add the internal Battery API
Date: Tue, 1 Dec 2020 11:15:02 -0800 [thread overview]
Message-ID: <CAO271mmD+MbWOScUXiFc2x0r0qOY+2yQF-39hbco4mK92qdpyw@mail.gmail.com> (raw)
In-Reply-To: <f2fbc270588a75ccebb8e14590b37b7c6bddab60.camel@hadess.net>
Hi Bastien,
I will send a separate patch to update the doc.
On Tue, Dec 1, 2020 at 8:29 AM Bastien Nocera <hadess@hadess.net> wrote:
>
> On Mon, 2020-11-30 at 16:27 -0800, Luiz Augusto von Dentz wrote:
> > Hi Sonny,
> > <snip>
> > Applied, thanks.
>
> Missed it :/
> Any chance you could update the org.bluez.BatteryProvider1 docs as per
> my review?
>
> Cheers
>
prev parent reply other threads:[~2020-12-01 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 21:55 [PATCH BlueZ v5 1/7] battery: Add the internal Battery API Sonny Sasaka
2020-11-30 21:55 ` [PATCH BlueZ v5 2/7] profiles/battery: Refactor to use battery library Sonny Sasaka
2020-11-30 21:55 ` [PATCH BlueZ v5 3/7] battery: Add Source property to Battery API Sonny Sasaka
2020-11-30 21:55 ` [PATCH BlueZ v5 4/7] doc: Add Battery Provider API doc Sonny Sasaka
2020-12-01 16:25 ` Bastien Nocera
2020-11-30 21:56 ` [PATCH BlueZ v5 5/7] test: Add test app for Battery Provider API Sonny Sasaka
2020-11-30 21:56 ` [PATCH BlueZ v5 6/7] adapter: Add a public function to find a device by path Sonny Sasaka
2020-12-01 16:27 ` Bastien Nocera
2020-11-30 21:56 ` [PATCH BlueZ v5 7/7] battery: Implement Battery Provider API Sonny Sasaka
2020-11-30 22:34 ` [BlueZ,v5,1/7] battery: Add the internal Battery API bluez.test.bot
2020-12-01 0:27 ` Luiz Augusto von Dentz
2020-12-01 16:29 ` Bastien Nocera
2020-12-01 19:15 ` Sonny Sasaka [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=CAO271mmD+MbWOScUXiFc2x0r0qOY+2yQF-39hbco4mK92qdpyw@mail.gmail.com \
--to=sonnysasaka@chromium.org \
--cc=hadess@hadess.net \
--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 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).