All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [BlueZ,1/2] adapter: Fix not using the correct setting
Date: Sat, 06 Mar 2021 11:10:30 +0100	[thread overview]
Message-ID: <2e29061ee96d62e4d744f9d71c8c4802aa782b6d.camel@hadess.net> (raw)
In-Reply-To: <CABBYNZL8wBc8OQvrRMXuqP=tB4ug2AAU0Ov3uCMvCcJUAz_Kiw@mail.gmail.com>

On Fri, 2021-03-05 at 17:17 -0800, Luiz Augusto von Dentz wrote:
> Hi,
> 
> On Thu, Mar 4, 2021 at 2:38 PM <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=442263
> > 
> > ---Test result---
> > 
> > ##############################
> > Test: CheckPatch - PASS
> > 
> > ##############################
> > Test: CheckGitLint - PASS
> > 
> > ##############################
> > Test: CheckBuild - PASS
> > 
> > ##############################
> > Test: MakeCheck - PASS
> > 
> > 
> > 
> > ---
> > Regards,
> > Linux Bluetooth
> 
> Applied.

You didn't reply to my question about the patch.

I can't wait until we don't have to use mailing-lists to submit
patches.

Sigh.



  reply	other threads:[~2021-03-06 10:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 22:24 [PATCH BlueZ 1/2] adapter: Fix not using the correct setting Luiz Augusto von Dentz
2021-03-04 22:24 ` [PATCH BlueZ 2/2] adapter: Return Busy error when setting is pending Luiz Augusto von Dentz
2021-03-04 22:38 ` [BlueZ,1/2] adapter: Fix not using the correct setting bluez.test.bot
2021-03-06  1:17   ` Luiz Augusto von Dentz
2021-03-06 10:10     ` Bastien Nocera [this message]
2021-03-05  7:34 ` [PATCH BlueZ 1/2] " 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=2e29061ee96d62e4d744f9d71c8c4802aa782b6d.camel@hadess.net \
    --to=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 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.