public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: kernel/trace/rv/rv.c:244: warning: Function parameter or member 'mdef' not described in 'rv_disable_monitor'
Date: Sun, 10 Dec 2023 00:04:37 +0800	[thread overview]
Message-ID: <202312100010.bWNK9nlA-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   f2e8a57ee9036c7d5443382b6c3c09b51a92ec7e
commit: 102227b970a15256f5ffd12a6a276ddf978e6caf rv: Add Runtime Verification (RV) interface
date:   1 year, 4 months ago
config: x86_64-buildonly-randconfig-004-20231010 (https://download.01.org/0day-ci/archive/20231210/202312100010.bWNK9nlA-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231210/202312100010.bWNK9nlA-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/202312100010.bWNK9nlA-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> kernel/trace/rv/rv.c:244: warning: Function parameter or member 'mdef' not described in 'rv_disable_monitor'
>> kernel/trace/rv/rv.c:255: warning: Function parameter or member 'mdef' not described in 'rv_enable_monitor'


vim +244 kernel/trace/rv/rv.c

   237	
   238	/**
   239	 * rv_disable_monitor - disable a given runtime monitor
   240	 *
   241	 * Returns 0 on success.
   242	 */
   243	int rv_disable_monitor(struct rv_monitor_def *mdef)
 > 244	{
   245		__rv_disable_monitor(mdef, true);
   246		return 0;
   247	}
   248	
   249	/**
   250	 * rv_enable_monitor - enable a given runtime monitor
   251	 *
   252	 * Returns 0 on success, error otherwise.
   253	 */
   254	int rv_enable_monitor(struct rv_monitor_def *mdef)
 > 255	{
   256		int retval;
   257	
   258		lockdep_assert_held(&rv_interface_lock);
   259	
   260		if (mdef->monitor->enabled)
   261			return 0;
   262	
   263		retval = mdef->monitor->enable();
   264	
   265		if (!retval)
   266			mdef->monitor->enabled = 1;
   267	
   268		return retval;
   269	}
   270	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2023-12-09 16:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202312100010.bWNK9nlA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bristot@kernel.org \
    --cc=linux-kernel@vger.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