From: Peng Fan <peng.fan@oss.nxp.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: use assign_bit() where applicable
Date: Mon, 21 Sep 2026 14:31:19 +0800 [thread overview]
Message-ID: <arDPNx/dR0ppjSEK@shlinux89> (raw)
In-Reply-To: <20260920072151.40637efd@fedora>
On Sun, Sep 20, 2026 at 07:21:51AM -0400, Steven Rostedt wrote:
>On Sun, 20 Sep 2026 10:28:10 +0800
>"Peng Fan (OSS)" <peng.fan@oss.nxp.com> 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:
>> /**
>> @@ -1673,10 +1670,8 @@ event_enable_trigger(struct event_trigger_data *data,
>> {
>> struct enable_trigger_data *enable_data = data->private_data;
>>
>> - if (enable_data->enable)
>> - clear_bit(EVENT_FILE_FL_SOFT_DISABLED_BIT, &enable_data->file->flags);
>> - else
>> - set_bit(EVENT_FILE_FL_SOFT_DISABLED_BIT, &enable_data->file->flags);
>> + assign_bit(EVENT_FILE_FL_SOFT_DISABLED_BIT, &enable_data->file->flags,
>> + !enable_data->enable);
>
>Ditto.
This will exceeds 100 columns. Should I keep as it is using two lines?
WARNING: line length of 101 exceeds 100 columns
#116: FILE: kernel/trace/trace_events_trigger.c:1673:
+ assign_bit(EVENT_FILE_FL_SOFT_DISABLED_BIT, &enable_data->file->flags, !enable_data->enable);
Thanks,
Peng
>
>Thanks,
>
>-- Steve
>
>> }
>>
>> static bool
>> diff --git a/kernel/trace/trace_events_user.c b/kernel/trace/trace_events_user.c
>> index f658c3a77aa7..055894cb999c 100644
>> --- a/kernel/trace/trace_events_user.c
>> +++ b/kernel/trace/trace_events_user.c
>> @@ -590,10 +590,7 @@ static int user_event_enabler_write(struct user_event_mm *mm,
>> ptr = kaddr + (uaddr & ~PAGE_MASK);
>>
>> /* Update bit atomically, user tracers must be atomic as well */
>> - if (enabler->event && enabler->event->status)
>> - set_bit(bit, ptr);
>> - else
>> - clear_bit(bit, ptr);
>> + assign_bit(bit, ptr, enabler->event && enabler->event->status);
>>
>> kunmap_local(kaddr);
>> unpin_user_pages_dirty_lock(&page, 1, true);
>
>
>
prev parent reply other threads:[~2026-09-21 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 2:28 Peng Fan (OSS)
2026-09-20 11:21 ` Steven Rostedt
2026-09-21 6:31 ` Peng Fan [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=arDPNx/dR0ppjSEK@shlinux89 \
--to=peng.fan@oss.nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=peng.fan@nxp.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®