From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ,v4,1/6] adapter: Keep track of whether the adapter is rfkill'ed
Date: Wed, 31 Aug 2022 13:36:30 +0200 [thread overview]
Message-ID: <77f437c81585829cc800379ee1fd3096ece092ac.camel@hadess.net> (raw)
In-Reply-To: <630f3693.c80a0220.658dc.628a@mx.google.com>
On Wed, 2022-08-31 at 03:23 -0700, bluez.test.bot@gmail.com wrote:
> This is automated email and please do not reply to this email!
>
> Dear submitter,
>
> Thank you for submitting the patches to the linux bluetooth mailing
> list.
> This is a CI test results with your patch series:
> PW
> Link:https://patchwork.kernel.org/project/bluetooth/list/?series=6727
> 64
>
> ---Test result---
>
> Test Summary:
> CheckPatch FAIL 9.12 seconds
All those should be fixed in v5.
next prev parent reply other threads:[~2022-08-31 11:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 9:19 [PATCH BlueZ v4 1/6] adapter: Keep track of whether the adapter is rfkill'ed Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 2/6] adapter: Implement PowerState property Bastien Nocera
2022-08-31 20:03 ` Luiz Augusto von Dentz
2022-09-01 10:43 ` Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 3/6] client: Print the " Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 4/6] adapter-api: Add PowerState property documentation Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 5/6] adapter: Fix typo in function name Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 6/6] adapter: Remove experimental flag for PowerState Bastien Nocera
2022-08-31 9:23 ` Bastien Nocera
2022-08-31 10:23 ` [BlueZ,v4,1/6] adapter: Keep track of whether the adapter is rfkill'ed bluez.test.bot
2022-08-31 11:36 ` Bastien Nocera [this message]
2022-08-31 11:36 ` [PATCH BlueZ v4 1/6] " Bastien Nocera
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=77f437c81585829cc800379ee1fd3096ece092ac.camel@hadess.net \
--to=hadess@hadess.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox