From: patchwork-bot+bluetooth@kernel.org
To: Simon Mikuda <simon.mikuda@streamunlimited.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/2] l2test: Enable hex input for PSM
Date: Tue, 28 Mar 2023 20:50:18 +0000 [thread overview]
Message-ID: <168003661843.8805.15121337504355290538.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230328052619.1357253-1-simon.mikuda@streamunlimited.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 28 Mar 2023 07:26:17 +0200 you wrote:
> Thanks for review. I'm sending updated patches.
>
> Simon Mikuda (2):
> l2test: Enable hex input for PSM
> l2test: Fix setting mode for BR/EDR l2cap socket
>
> lib/l2cap.h | 2 ++
> tools/l2test.c | 24 ++++++++++++++++++++++--
> 2 files changed, 24 insertions(+), 2 deletions(-)
Here is the summary with links:
- [BlueZ,v2,1/2] l2test: Enable hex input for PSM
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=cedace72c3f7
- [BlueZ,v2,2/2] l2test: Fix setting mode for BR/EDR l2cap socket
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-28 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 10:27 [PATCH BlueZ 0/2] l2test fix+feature Simon Mikuda
2023-03-23 10:27 ` [PATCH BlueZ 1/2] l2test: Enable hex input for PSM Simon Mikuda
2023-03-23 11:42 ` l2test fix+feature bluez.test.bot
2023-03-23 17:20 ` [PATCH BlueZ 1/2] l2test: Enable hex input for PSM Luiz Augusto von Dentz
2023-03-28 5:26 ` [PATCH BlueZ v2 0/2] " Simon Mikuda
2023-03-28 5:26 ` [PATCH BlueZ v2 1/2] " Simon Mikuda
2023-03-28 6:57 ` bluez.test.bot
2023-03-28 5:26 ` [PATCH BlueZ v2 2/2] l2test: Fix setting mode for BR/EDR l2cap socket Simon Mikuda
2023-03-28 20:50 ` patchwork-bot+bluetooth [this message]
2023-03-23 10:27 ` [PATCH BlueZ " Simon Mikuda
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=168003661843.8805.15121337504355290538.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon.mikuda@streamunlimited.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.