All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: patchwork-bot+bluetooth@kernel.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v7 1/6] adapter: Keep track of whether the adapter is rfkill'ed
Date: Thu, 01 Sep 2022 22:10:07 +0200	[thread overview]
Message-ID: <507eb017ee07075386127b40a35765513cf8de4b.camel@hadess.net> (raw)
In-Reply-To: <166205821606.5769.2196808396648976031.git-patchwork-notify@kernel.org>

On Thu, 2022-09-01 at 18:50 +0000, patchwork-bot+bluetooth@kernel.org
wrote:
> Hello:
> 
> This series was applied to bluetooth/bluez.git (master)
> by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
> 
> On Thu,  1 Sep 2022 13:07:14 +0200 you wrote:
> > Instead of only replying to D-Bus requests with an error saying the
> > adapter is blocked, keep track of the rfkill being enabled or
> > disabled
> > so we know the rfkill state of the adapter at all times.
> > ---
> >  src/adapter.c | 25 +++++++++++++--
> >  src/adapter.h |  1 +
> >  src/btd.h     |  1 +
> >  src/rfkill.c  | 89 ++++++++++++++++++++++++++++++++++++++---------
> > ----
> >  4 files changed, 91 insertions(+), 25 deletions(-)
> 
> Here is the summary with links:
>   - [BlueZ,v7,1/6] adapter: Keep track of whether the adapter is
> rfkill'ed
>    
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=abf5ba6b80ad
>   - [BlueZ,v7,2/6] adapter: Implement PowerState property
>    
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=58021a665b7f
>   - [BlueZ,v7,3/6] client: Print the PowerState property
>    
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=48992da64f52
>   - [BlueZ,v7,4/6] adapter-api: Add PowerState property documentation
>    
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6e49216ad47d
>   - [BlueZ,v7,5/6] adapter: Fix typo in function name
>    
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=61f4f2895882
>   - [BlueZ,v7,6/6] adapter: Remove experimental flag for PowerState
>     (no matching commit)
> 
> You are awesome, thank you!

Sweet, thanks!

The links are missing "commit/" in the URL though, so should be:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=abf5ba6b80ad
not:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=abf5ba6b80ad

      reply	other threads:[~2022-09-01 20:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 11:07 [PATCH BlueZ v7 1/6] adapter: Keep track of whether the adapter is rfkill'ed Bastien Nocera
2022-09-01 11:07 ` [PATCH BlueZ v7 2/6] adapter: Implement PowerState property Bastien Nocera
2022-09-01 11:07 ` [PATCH BlueZ v7 3/6] client: Print the " Bastien Nocera
2022-09-01 11:07 ` [PATCH BlueZ v7 4/6] adapter-api: Add PowerState property documentation Bastien Nocera
2022-09-01 11:07 ` [PATCH BlueZ v7 5/6] adapter: Fix typo in function name Bastien Nocera
2022-09-01 11:07 ` [PATCH BlueZ v7 6/6] adapter: Remove experimental flag for PowerState Bastien Nocera
2022-11-13 15:54   ` Jonas Dreßler
2022-11-14 23:35     ` Luiz Augusto von Dentz
2022-11-17 14:18     ` Bastien Nocera
2022-09-01 12:18 ` [BlueZ,v7,1/6] adapter: Keep track of whether the adapter is rfkill'ed bluez.test.bot
2022-09-01 18:50 ` [PATCH BlueZ v7 1/6] " patchwork-bot+bluetooth
2022-09-01 20:10   ` Bastien Nocera [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=507eb017ee07075386127b40a35765513cf8de4b.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=patchwork-bot+bluetooth@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.