From: patchwork-bot+bluetooth@kernel.org
To: Arnaud Bonnet <abo@medichon.fr>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org, skhan@linuxfoundation.org,
jkoolstra@xs4all.nl
Subject: Re: [PATCH v2] Bluetooth: btmtk: remove redundant memory barrier with helper
Date: Fri, 23 Oct 2026 21:00:38 +0000 [thread overview]
Message-ID: <179278923809.1268720.9672691636919611279.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261023093645.4669-1-abo@medichon.fr>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 23 Oct 2026 11:36:45 +0200 you wrote:
> The test_and_clear_bit() call works as a full memory barrier, thus it is
> not required to emit a barrier using smp_mb__after_atomic() before
> wake_up_bit().
>
> Replace the whole sequences with test_and_clear_wake_up_bit(), which was
> introduced later in commit 52d633def56c ("sched: Add
> test_and_clear_wake_up_bit() and atomic_dec_and_wake_up()") as a wrapper
> for the correct sequence.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: btmtk: remove redundant memory barrier with helper
https://git.kernel.org/bluetooth/bluetooth-next/c/ebb8ee296578
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-23 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 9:36 [PATCH v2] Bluetooth: btmtk: remove redundant memory barrier with helper Arnaud Bonnet
2026-10-23 12:56 ` [v2] " bluez.test.bot
2026-10-23 21:00 ` 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=179278923809.1268720.9672691636919611279.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=abo@medichon.fr \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jkoolstra@xs4all.nl \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox