public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Stefan Berger <stefanb@linux.ibm.com>
Subject: [jarkko-tpmdd:next 15/38] drivers/char/tpm/tpm-buf.c:62: warning: Function parameter or struct member 'buf' not described in 'tpm_buf_length'
Date: Mon, 6 May 2024 08:08:27 +0800	[thread overview]
Message-ID: <202405060827.XuRaAHPt-lkp@intel.com> (raw)

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git next
head:   152585665f0f6b89e67ed6d04c17b18d1f0f4077
commit: 28a0675aa9964fd89e61248d4cfe49baf9151199 [15/38] tpm: Store the length of the tpm_buf data separately.
config: s390-defconfig (https://download.01.org/0day-ci/archive/20240506/202405060827.XuRaAHPt-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 37ae4ad0eef338776c7e2cffb3896153d43dcd90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240506/202405060827.XuRaAHPt-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/202405060827.XuRaAHPt-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/char/tpm/tpm-buf.c:62: warning: Function parameter or struct member 'buf' not described in 'tpm_buf_length'


vim +62 drivers/char/tpm/tpm-buf.c

eb0a137505fd0b James Bottomley 2024-04-29  55  
28a0675aa9964f Jarkko Sakkinen 2024-04-29  56  /**
28a0675aa9964f Jarkko Sakkinen 2024-04-29  57   * tpm_buf_length() - Return the number of bytes consumed by the data
28a0675aa9964f Jarkko Sakkinen 2024-04-29  58   *
28a0675aa9964f Jarkko Sakkinen 2024-04-29  59   * Return: The number of bytes consumed by the buffer
28a0675aa9964f Jarkko Sakkinen 2024-04-29  60   */
eb0a137505fd0b James Bottomley 2024-04-29  61  u32 tpm_buf_length(struct tpm_buf *buf)
eb0a137505fd0b James Bottomley 2024-04-29 @62  {
28a0675aa9964f Jarkko Sakkinen 2024-04-29  63  	return buf->length;
eb0a137505fd0b James Bottomley 2024-04-29  64  }
eb0a137505fd0b James Bottomley 2024-04-29  65  EXPORT_SYMBOL_GPL(tpm_buf_length);
eb0a137505fd0b James Bottomley 2024-04-29  66  

:::::: The code at line 62 was first introduced by commit
:::::: eb0a137505fd0baf693173f3572b87e983bc0594 tpm: Move buffer handling from static inlines to real functions

:::::: TO: James Bottomley <James.Bottomley@HansenPartnership.com>
:::::: CC: Jarkko Sakkinen <jarkko@kernel.org>

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

             reply	other threads:[~2024-05-06  0:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  0:08 kernel test robot [this message]
2024-05-07 20:00 ` [jarkko-tpmdd:next 15/38] drivers/char/tpm/tpm-buf.c:62: warning: Function parameter or struct member 'buf' not described in 'tpm_buf_length' Jarkko Sakkinen

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=202405060827.XuRaAHPt-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=jarkko@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=stefanb@linux.ibm.com \
    /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