The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tingwei Zhang <tingwei@codeaurora.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: drivers/hwtracing/stm/ftrace.c:38: warning: Function parameter or struct member 'export' not described in 'stm_ftrace_write'
Date: Fri, 27 Dec 2024 23:35:28 +0800	[thread overview]
Message-ID: <202412280133.JV62su59-lkp@intel.com> (raw)

Hi Tingwei,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   d6ef8b40d075c425f548002d2f35ae3f06e9cf96
commit: 7b9749bd830848bca9179b0a16251ca3c36e82e6 stm class: ftrace: Change dependency to TRACING
date:   4 years, 3 months ago
config: sh-randconfig-001-20241212 (https://download.01.org/0day-ci/archive/20241228/202412280133.JV62su59-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241228/202412280133.JV62su59-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/202412280133.JV62su59-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/hwtracing/stm/ftrace.c:38: warning: Function parameter or struct member 'export' not described in 'stm_ftrace_write'


vim +38 drivers/hwtracing/stm/ftrace.c

262e1f6e39143c Chunyan Zhang 2016-11-21  30  
262e1f6e39143c Chunyan Zhang 2016-11-21  31  /**
262e1f6e39143c Chunyan Zhang 2016-11-21  32   * stm_ftrace_write() - write data to STM via 'stm_ftrace' source
262e1f6e39143c Chunyan Zhang 2016-11-21  33   * @buf:	buffer containing the data packet
262e1f6e39143c Chunyan Zhang 2016-11-21  34   * @len:	length of the data packet
262e1f6e39143c Chunyan Zhang 2016-11-21  35   */
262e1f6e39143c Chunyan Zhang 2016-11-21  36  static void notrace
a773d419275bf5 Felipe Balbi  2017-06-02  37  stm_ftrace_write(struct trace_export *export, const void *buf, unsigned int len)
262e1f6e39143c Chunyan Zhang 2016-11-21 @38  {
a773d419275bf5 Felipe Balbi  2017-06-02  39  	struct stm_ftrace *stm = container_of(export, struct stm_ftrace, ftrace);
a773d419275bf5 Felipe Balbi  2017-06-02  40  
a773d419275bf5 Felipe Balbi  2017-06-02  41  	stm_source_write(&stm->data, STM_FTRACE_CHAN, buf, len);
262e1f6e39143c Chunyan Zhang 2016-11-21  42  }
262e1f6e39143c Chunyan Zhang 2016-11-21  43  

:::::: The code at line 38 was first introduced by commit
:::::: 262e1f6e39143c2a0f559e2fb4a835069a7693a9 stm class: ftrace: Add ftrace-export-over-stm driver

:::::: TO: Chunyan Zhang <zhang.chunyan@linaro.org>
:::::: CC: Steven Rostedt <rostedt@goodmis.org>

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

             reply	other threads:[~2024-12-27 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27 15:35 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-03 17:26 drivers/hwtracing/stm/ftrace.c:38: warning: Function parameter or struct member 'export' not described in 'stm_ftrace_write' kernel test robot

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=202412280133.JV62su59-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=tingwei@codeaurora.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