public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/2] monitor/att: Add initial decoding for HIDS attributes
Date: Mon, 02 Feb 2026 16:40:04 +0000	[thread overview]
Message-ID: <177005040463.1106893.4832508792487556852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260130155637.1150573-1-luiz.dentz@gmail.com>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Fri, 30 Jan 2026 10:56:36 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This adds decoders to HID Information and HID Control Point
> characteristics.
> ---
>  monitor/att.c | 82 +++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 82 insertions(+)

Here is the summary with links:
  - [BlueZ,v1,1/2] monitor/att: Add initial decoding for HIDS attributes
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ba27f7a12246
  - [BlueZ,v1,2/2] monitor/att: Fix printing data twice
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4c963f21e56a

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



      parent reply	other threads:[~2026-02-02 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 15:56 [PATCH BlueZ v1 1/2] monitor/att: Add initial decoding for HIDS attributes Luiz Augusto von Dentz
2026-01-30 15:56 ` [PATCH BlueZ v1 2/2] monitor/att: Fix printing data twice Luiz Augusto von Dentz
2026-01-30 17:09 ` [BlueZ,v1,1/2] monitor/att: Add initial decoding for HIDS attributes bluez.test.bot
2026-02-02 16:40 ` patchwork-bot+bluetooth [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=177005040463.1106893.4832508792487556852.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --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