All of lore.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 1/2] monitor/att: Add handler support for Read by Type
Date: Mon, 07 Nov 2022 19:10:15 +0000	[thread overview]
Message-ID: <166784821526.7961.4470930074464027915.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221104213649.36925-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,  4 Nov 2022 14:36:48 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This adds handler support for Read by Type so it can further decode
> the values when the procedure is used.
> ---
>  monitor/att.c   | 206 ++++++++++++++++++++++++++++++++++--------------
>  monitor/l2cap.h |  13 ++-
>  2 files changed, 155 insertions(+), 64 deletions(-)

Here is the summary with links:
  - [BlueZ,1/2] monitor/att: Add handler support for Read by Type
    (no matching commit)
  - [BlueZ,2/2] monitor/att: Add support for decoding Characteristic Declaration
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7e0e08ca5396

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-11-07 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 21:36 [PATCH BlueZ 1/2] monitor/att: Add handler support for Read by Type Luiz Augusto von Dentz
2022-11-04 21:36 ` [PATCH BlueZ 2/2] monitor/att: Add support for decoding Characteristic Declaration Luiz Augusto von Dentz
2022-11-04 22:23 ` [BlueZ,1/2] monitor/att: Add handler support for Read by Type bluez.test.bot
2022-11-07 19:10 ` 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=166784821526.7961.4470930074464027915.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 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.