From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: kernel test robot <lkp@intel.com>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
oe-kbuild-all@lists.linux.dev,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Add an option to show symbols in _text+offset for function profiler
Date: Sun, 21 Sep 2025 23:14:30 +0900 [thread overview]
Message-ID: <20250921231430.66a0da9e185ea1084bc6d301@kernel.org> (raw)
In-Reply-To: <20250919131621.093295c8@gandalf.local.home>
On Fri, 19 Sep 2025 13:16:21 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sat, 20 Sep 2025 01:09:52 +0800
> kernel test robot <lkp@intel.com> wrote:
>
> > Hi Masami,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on trace/for-next]
> > [also build test ERROR on linus/master v6.17-rc6 next-20250918]
> > [If your patch is applied to the wrong git tree, kindly drop us a note.
> > And when submitting patch, we suggest to use '--base' as documented in
> > https://git-scm.com/docs/git-format-patch#_base_tree_information]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Masami-Hiramatsu-Google/tracing-Add-an-option-to-show-symbols-in-_text-offset-for-function-profiler/20250919-135733
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
> > patch link: https://lore.kernel.org/r/175826135058.101165.7219957344129610147.stgit%40devnote2
> > patch subject: [PATCH] tracing: Add an option to show symbols in _text+offset for function profiler
> > config: x86_64-buildonly-randconfig-002-20250919 (https://download.01.org/0day-ci/archive/20250920/202509200000.EJ4InVti-lkp@intel.com/config)
> > compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250920/202509200000.EJ4InVti-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202509200000.EJ4InVti-lkp@intel.com/
> >
> > All error/warnings (new ones prefixed by >>):
> >
> > In file included from kernel/trace/trace_sched_switch.c:15:
> > >> kernel/trace/trace.h:1422:37: warning: left shift count >= width of type [-Wshift-count-overflow]
> > 1422 | #define C(a, b) TRACE_ITER_##a = (1 << TRACE_ITER_##a##_BIT)
> > | ^~
>
> Ouch! We need to make the option enum64 now!
Ah, it is an enum, not macro.
Thanks!
>
> -- Steve
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2025-09-21 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 5:55 [PATCH] tracing: Add an option to show symbols in _text+offset for function profiler Masami Hiramatsu (Google)
2025-09-19 17:09 ` kernel test robot
2025-09-20 9:06 ` Masami Hiramatsu
2025-09-19 17:09 ` kernel test robot
2025-09-19 17:16 ` Steven Rostedt
2025-09-21 14:14 ` Masami Hiramatsu [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=20250921231430.66a0da9e185ea1084bc6d301@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).