public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC V2 01/21] rv: Add Runtime Verification (RV) interface
Date: Tue, 15 Feb 2022 01:50:45 +0800	[thread overview]
Message-ID: <202202150143.3BpCqVdF-lkp@intel.com> (raw)
In-Reply-To: <87606fc180e4551b19dc61609907b555214c41a1.1644830251.git.bristot@kernel.org>

Hi Daniel,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on rostedt-trace/for-next]
[also build test WARNING on lwn/docs-next linus/master v5.17-rc4 next-20220214]
[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]

url:    https://github.com/0day-ci/linux/commits/Daniel-Bristot-de-Oliveira/The-Runtime-Verification-RV-interface/20220214-193144
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git for-next
config: hexagon-allyesconfig (https://download.01.org/0day-ci/archive/20220215/202202150143.3BpCqVdF-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project ea071884b0cc7210b3cc5fe858f0e892a779a23b)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/f99370d1c81f0a3b56d6630ff62631f6ecfdf8d8
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Daniel-Bristot-de-Oliveira/The-Runtime-Verification-RV-interface/20220214-193144
        git checkout f99370d1c81f0a3b56d6630ff62631f6ecfdf8d8
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash kernel/trace/rv/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> kernel/trace/rv/rv.c:189:6: warning: no previous prototype for function 'disable_monitor' [-Wmissing-prototypes]
   void disable_monitor(struct rv_monitor_def *mdef)
        ^
   kernel/trace/rv/rv.c:189:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   void disable_monitor(struct rv_monitor_def *mdef)
   ^
   static 
>> kernel/trace/rv/rv.c:202:6: warning: no previous prototype for function 'enable_monitor' [-Wmissing-prototypes]
   void enable_monitor(struct rv_monitor_def *mdef)
        ^
   kernel/trace/rv/rv.c:202:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   void enable_monitor(struct rv_monitor_def *mdef)
   ^
   static 
   2 warnings generated.


vim +/disable_monitor +189 kernel/trace/rv/rv.c

   185	
   186	/*
   187	 * Disable a given runtime monitor.
   188	 */
 > 189	void disable_monitor(struct rv_monitor_def *mdef)
   190	{
   191		if (mdef->monitor->enabled) {
   192			mdef->monitor->enabled = 0;
   193			mdef->monitor->stop();
   194		}
   195	
   196		mdef->enabled = 0;
   197	}
   198	
   199	/*
   200	 * Enable a given monitor.
   201	 */
 > 202	void enable_monitor(struct rv_monitor_def *mdef)
   203	{
   204		/*
   205		 * Reset all internal monitors before starting.
   206		 */
   207		mdef->monitor->reset();
   208		if (!mdef->monitor->enabled)
   209			mdef->monitor->start();
   210	
   211		mdef->monitor->enabled = 1;
   212		mdef->enabled = 1;
   213	}
   214	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

           reply	other threads:[~2022-02-14 17:51 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87606fc180e4551b19dc61609907b555214c41a1.1644830251.git.bristot@kernel.org>]

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=202202150143.3BpCqVdF-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bristot@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    /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