mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Peng Fan <peng.fan@oss.nxp.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, kees@kernel.org,
	nicoyip.dev@gmail.com, aliamemis@disroot.org, kuba@kernel.org,
	imv4bel@gmail.com, pengpeng@iscas.ac.cn, suunj1331@gmail.com,
	tim.bird@sony.com, peng.fan@nxp.com, leitao@debian.org,
	jcperdomo100@gmail.com, safa.karakus@secunnix.com,
	rollkingzzc@gmail.com, linux-kernel@vger.kernel.org,
	luiz.von.dentz@intel.com, oss@fourdim.xyz, pav@iki.fi,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: use assign_bit() where applicable
Date: Mon, 21 Sep 2026 14:10:07 +0000	[thread overview]
Message-ID: <178999980714.3047822.7600652499809584862.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260920022610.3145618-1-peng.fan@oss.nxp.com>

Hello:

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

On Sun, 20 Sep 2026 10:26:02 +0800 you wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> Convert open-coded if/else with set_bit/clear_bit the assign_bit API.
> 
> Done with Coccinelle semantic patch:
>     // set_bit -> clear_bit => assign_bit
> 
> [...]

Here is the summary with links:
  - Bluetooth: use assign_bit() where applicable
    https://git.kernel.org/bluetooth/bluetooth-next/c/5f639837ba47

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



      reply	other threads:[~2026-09-21 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20  2:26 Peng Fan (OSS)
2026-09-21 14: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=178999980714.3047822.7600652499809584862.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=aliamemis@disroot.org \
    --cc=imv4bel@gmail.com \
    --cc=jcperdomo100@gmail.com \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=nicoyip.dev@gmail.com \
    --cc=oss@fourdim.xyz \
    --cc=pav@iki.fi \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=pengpeng@iscas.ac.cn \
    --cc=rollkingzzc@gmail.com \
    --cc=safa.karakus@secunnix.com \
    --cc=suunj1331@gmail.com \
    --cc=tim.bird@sony.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
all inboxes | Powered by JetHome®