All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Joseph Hwang <josephsih@chromium.org>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	luiz.dentz@gmail.com, pali@kernel.org, josephsih@google.com,
	chromeos-bluetooth-upstreaming@chromium.org
Subject: Re: [BlueZ PATCH v6 1/8] doc: Introduce the quality report command and event
Date: Thu, 02 Jun 2022 16:00:12 +0000	[thread overview]
Message-ID: <165418561283.15613.7221303146796113568.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220526112456.2488536-1-josephsih@chromium.org>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Marcel Holtmann <marcel@holtmann.org>:

On Thu, 26 May 2022 19:24:49 +0800 you wrote:
> Add the MGMT quality report command and event in doc/mgmt-api.txt.
> 
> ---
> 
> Changes in v6:
> - No update in this patch. The patch 3/8 is updated to resolve a
>   patch conflict.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v6,1/8] doc: Introduce the quality report command and event
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=93850c827d54
  - [BlueZ,v6,2/8] lib: Add structures and constants for quality report command and event
    (no matching commit)
  - [BlueZ,v6,3/8] adapter: remove quality report from experimental features
    (no matching commit)
  - [BlueZ,v6,4/8] adapter: support AOSP MGMT_EV_QUALITY_REPORT
    (no matching commit)
  - [BlueZ,v6,5/8] adapter: support Intel MGMT_EV_QUALITY_REPORT
    (no matching commit)
  - [BlueZ,v6,6/8] tools/btmgmt: fix quality report command
    (no matching commit)
  - [BlueZ,v6,7/8] monitor: print quality report cmd
    (no matching commit)
  - [BlueZ,v6,8/8] monitor: packet: add missing decodings of MGMT commands to todo
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2022-06-02 16:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 11:24 [BlueZ PATCH v6 1/8] doc: Introduce the quality report command and event Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 2/8] lib: Add structures and constants for " Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 3/8] adapter: remove quality report from experimental features Joseph Hwang
2022-05-26 20:31   ` Luiz Augusto von Dentz
2022-05-27  3:13     ` Joseph Hwang
2022-05-30 21:02       ` Luiz Augusto von Dentz
2022-05-26 11:24 ` [BlueZ PATCH v6 4/8] adapter: support AOSP MGMT_EV_QUALITY_REPORT Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 5/8] adapter: support Intel MGMT_EV_QUALITY_REPORT Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 6/8] tools/btmgmt: fix quality report command Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 7/8] monitor: print quality report cmd Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 8/8] monitor: packet: add missing decodings of MGMT commands to todo Joseph Hwang
2022-05-26 15:39 ` [BlueZ,v6,1/8] doc: Introduce the quality report command and event bluez.test.bot
2022-06-02 16:00 ` patchwork-bot+bluetooth [this message]
2022-06-07  6:40   ` [BlueZ PATCH v6 1/8] " Joseph Hwang

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=165418561283.15613.7221303146796113568.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=chromeos-bluetooth-upstreaming@chromium.org \
    --cc=josephsih@chromium.org \
    --cc=josephsih@google.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pali@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.