[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251025153624.4b049170@batman.local.home>
Date: Sat, 25 Oct 2025 15:36:24 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Yury Norov (NVIDIA)" <yury.norov@...il.com>
Cc: Linus Walleij <linus.walleij@...aro.org>, Lee Jones <lee@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Masami
Hiramatsu <mhiramat@...nel.org>, Mark Rutland <mark.rutland@....com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH 13/21] trace: don't use GENMASK()
On Sat, 25 Oct 2025 15:29:54 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Sat, 25 Oct 2025 12:32:55 -0400
> "Yury Norov (NVIDIA)" <yury.norov@...il.com> wrote:
>
> > GENMASK(high, low) notation is confusing. FIRST_BITS() is more
> > appropriate.
> >
>
> I'm fine with this change as a clean up, but...
>
> > Signed-off-by: Yury Norov (NVIDIA) <yury.norov@...il.com>
> > ---
> > kernel/trace/fgraph.c | 10 +++++-----
> > kernel/trace/trace_probe.h | 2 +-
>
> Make this two different patches. trace_probe and fgraph go through
> different topic branches.
OK, I see this is part of a patch series that adds FIRST_BITS().
Please add that first, and the rest of the patches can go though their
individual trees. Something like this change I would like to make sure
doesn't accidentally cause a regression. That means it must go through
my tests before it gets applied.
-- Steve
Powered by blists - more mailing lists