From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: kernel test robot <lkp@intel.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Cc: oe-kbuild-all@lists.linux.dev, Juri Lelli <juri.lelli@redhat.com>,
William White <chwhite@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH V2 3/3] tracing/timerlat: Add user-space interface
Date: Thu, 25 May 2023 16:16:06 +0200 [thread overview]
Message-ID: <4f8f78c4-2af5-5089-a243-2df1c7cfb2d3@kernel.org> (raw)
In-Reply-To: <202305242020.VlsOXEMn-lkp@intel.com>
On 5/24/23 14:48, kernel test robot wrote:
> Hi Daniel,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v6.4-rc3 next-20230524]
> [cannot apply to rostedt-trace/for-next rostedt-trace/for-next-urgent]
> [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/Daniel-Bristot-de-Oliveira/tracing-osnoise-Switch-from-PF_NO_SETAFFINITY-to-migrate_disable/20230524-012512
> base: linus/master
> patch link: https://lore.kernel.org/r/a7b2c215c763e95a56fa1258743332b570c81c9d.1684860626.git.bristot%40kernel.org
> patch subject: [PATCH V2 3/3] tracing/timerlat: Add user-space interface
> config: i386-randconfig-i014-20230523
> compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
> reproduce (this is a W=1 build):
> # https://github.com/intel-lab-lkp/linux/commit/89216b54eaf490480bc1929f5780f95a688a91bb
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Daniel-Bristot-de-Oliveira/tracing-osnoise-Switch-from-PF_NO_SETAFFINITY-to-migrate_disable/20230524-012512
> git checkout 89216b54eaf490480bc1929f5780f95a688a91bb
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> make W=1 O=build_dir ARCH=i386 olddefconfig
> make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash kernel/trace/
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202305242020.VlsOXEMn-lkp@intel.com/
>
> All error/warnings (new ones prefixed by >>):
>
> kernel/trace/trace_osnoise.c: In function 'timerlat_fd_open':
>>> kernel/trace/trace_osnoise.c:2364:16: error: implicit declaration of function 'this_cpu_tmr_var'; did you mean 'this_cpu_osn_var'? [-Werror=implicit-function-declaration]
> 2364 | tlat = this_cpu_tmr_var();
> | ^~~~~~~~~~~~~~~~
> | this_cpu_osn_var
Thanks robot, I forgot to test without timerlat enabled. Easy to fix, an ifdef
here and there.
-- Daniel
next prev parent reply other threads:[~2023-05-25 14:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 17:22 [PATCH V2 0/3] osnoise/timerlat improvements Daniel Bristot de Oliveira
2023-05-23 17:22 ` [PATCH V2 1/3] tracing/osnoise: Switch from PF_NO_SETAFFINITY to migrate_disable Daniel Bristot de Oliveira
2023-05-23 17:22 ` [PATCH V2 2/3] tracing/osnoise: Skip running osnoise if all instances are off Daniel Bristot de Oliveira
2023-05-23 17:22 ` [PATCH V2 3/3] tracing/timerlat: Add user-space interface Daniel Bristot de Oliveira
2023-05-23 20:59 ` kernel test robot
2023-05-24 8:04 ` kernel test robot
2023-05-24 8:04 ` kernel test robot
2023-05-24 12:48 ` kernel test robot
2023-05-25 14:16 ` Daniel Bristot de Oliveira [this message]
2023-05-25 17:00 ` Daniel Bristot de Oliveira
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=4f8f78c4-2af5-5089-a243-2df1c7cfb2d3@kernel.org \
--to=bristot@kernel.org \
--cc=chwhite@redhat.com \
--cc=corbet@lwn.net \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mhiramat@kernel.org \
--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).