All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Helge Deller <deller@gmx.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: drivers/firmware/broadcom/tee_bnxt_fw.c:62: warning: Function parameter or struct member 'fw_shm_pool' not described in 'tee_bnxt_fw_private'
Date: Sat, 4 Jan 2025 10:03:23 +0800	[thread overview]
Message-ID: <202501041056.PcirM7AJ-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   63676eefb7a026d04b51dcb7aaf54f358517a2ec
commit: 024f5b597564acced9e69305f7a9ef1202186a61 parisc: Add qemu fw_cfg interface
date:   4 years, 3 months ago
config: parisc-randconfig-r025-20211224 (https://download.01.org/0day-ci/archive/20250104/202501041056.PcirM7AJ-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250104/202501041056.PcirM7AJ-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/202501041056.PcirM7AJ-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/firmware/broadcom/tee_bnxt_fw.c:62: warning: Function parameter or struct member 'fw_shm_pool' not described in 'tee_bnxt_fw_private'


vim +62 drivers/firmware/broadcom/tee_bnxt_fw.c

246880958ac939 Vikas Gupta 2019-10-31  50  
246880958ac939 Vikas Gupta 2019-10-31  51  /**
246880958ac939 Vikas Gupta 2019-10-31  52   * struct tee_bnxt_fw_private - OP-TEE bnxt private data
246880958ac939 Vikas Gupta 2019-10-31  53   * @dev:		OP-TEE based bnxt device.
246880958ac939 Vikas Gupta 2019-10-31  54   * @ctx:		OP-TEE context handler.
246880958ac939 Vikas Gupta 2019-10-31  55   * @session_id:		TA session identifier.
246880958ac939 Vikas Gupta 2019-10-31  56   */
246880958ac939 Vikas Gupta 2019-10-31  57  struct tee_bnxt_fw_private {
246880958ac939 Vikas Gupta 2019-10-31  58  	struct device *dev;
246880958ac939 Vikas Gupta 2019-10-31  59  	struct tee_context *ctx;
246880958ac939 Vikas Gupta 2019-10-31  60  	u32 session_id;
246880958ac939 Vikas Gupta 2019-10-31  61  	struct tee_shm *fw_shm_pool;
246880958ac939 Vikas Gupta 2019-10-31 @62  };
246880958ac939 Vikas Gupta 2019-10-31  63  

:::::: The code at line 62 was first introduced by commit
:::::: 246880958ac93989c97c73ae1e60b78b4c4c88c5 firmware: broadcom: add OP-TEE based BNXT f/w manager

:::::: TO: Vikas Gupta <vikas.gupta@broadcom.com>
:::::: CC: David S. Miller <davem@davemloft.net>

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

             reply	other threads:[~2025-01-04  2:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-04  2:03 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-06 10:07 drivers/firmware/broadcom/tee_bnxt_fw.c:62: warning: Function parameter or struct member 'fw_shm_pool' not described in 'tee_bnxt_fw_private' kernel test robot
2025-01-08  7:51 kernel test robot
2024-12-22 22:12 kernel test robot
2024-12-23  1:18 ` Philip Li

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=202501041056.PcirM7AJ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.