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 v3 1/2] shared/uhid: Fix registering UHID_START multiple times
Date: Tue, 13 Aug 2024 15:50:30 +0000	[thread overview]
Message-ID: <172356423051.1679641.15765907778343921260.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240813142935.504400-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 Tue, 13 Aug 2024 10:29:34 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> UHID_START callback shall only be registered once otherwise there is a
> risk of processing input queue multiple times.
> ---
>  src/shared/uhid.c | 13 ++++++++++---
>  unit/test-uhid.c  |  4 +++-
>  2 files changed, 13 insertions(+), 4 deletions(-)

Here is the summary with links:
  - [BlueZ,v3,1/2] shared/uhid: Fix registering UHID_START multiple times
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ee39d01fb9ee
  - [BlueZ,v3,2/2] shared/uhid: Fix not cleanup input queue on destroy
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a13638e6ae38

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



  parent reply	other threads:[~2024-08-13 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 14:29 [PATCH BlueZ v3 1/2] shared/uhid: Fix registering UHID_START multiple times Luiz Augusto von Dentz
2024-08-13 14:29 ` [PATCH BlueZ v3 2/2] shared/uhid: Fix not cleanup input queue on destroy Luiz Augusto von Dentz
2024-08-13 15:50 ` patchwork-bot+bluetooth [this message]
2024-08-13 16:31 ` [BlueZ,v3,1/2] shared/uhid: Fix registering UHID_START multiple times bluez.test.bot

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=172356423051.1679641.15765907778343921260.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.