lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <202412310834.jtCJj4oz-lkp@intel.com>
Date: Tue, 31 Dec 2024 08:35:23 +0800
From: kernel test robot <lkp@...el.com>
To: Timur Tabi <ttabi@...dia.com>
Cc: oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org,
	Danilo Krummrich <dakr@...hat.com>
Subject: drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:1117: warning: cannot
 understand function prototype: 'struct registry_list_entry '

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   ccb98ccef0e543c2bd4ef1a72270461957f3d8d0
commit: b58a0bc904ffa091fc020f7fd00e91808fec820e nouveau: add command-line GSP-RM registry support
date:   8 months ago
config: mips-randconfig-c004-20220208 (https://download.01.org/0day-ci/archive/20241231/202412310834.jtCJj4oz-lkp@intel.com/config)
compiler: mips64el-linux-gcc (GCC) 12.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241231/202412310834.jtCJj4oz-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202412310834.jtCJj4oz-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:1117: warning: cannot understand function prototype: 'struct registry_list_entry '
>> drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:1320: warning: cannot understand function prototype: 'const struct nv_gsp_registry_entries r535_registry_entries[] = '


vim +1117 drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c

  1093	
  1094	/**
  1095	 * registry_list_entry - linked list member for a registry key/value
  1096	 * @head: list_head struct
  1097	 * @type: dword, binary, or string
  1098	 * @klen: the length of name of the key
  1099	 * @vlen: the length of the value
  1100	 * @key: the key name
  1101	 * @dword: the data, if REGISTRY_TABLE_ENTRY_TYPE_DWORD
  1102	 * @binary: the data, if TYPE_BINARY or TYPE_STRING
  1103	 *
  1104	 * Every registry key/value is represented internally by this struct.
  1105	 *
  1106	 * Type DWORD is a simple 32-bit unsigned integer, and its value is stored in
  1107	 * @dword.
  1108	 *
  1109	 * Types BINARY and STRING are variable-length binary blobs.  The only real
  1110	 * difference between BINARY and STRING is that STRING is null-terminated and
  1111	 * is expected to contain only printable characters.
  1112	 *
  1113	 * Note: it is technically possible to have multiple keys with the same name
  1114	 * but different types, but this is not useful since GSP-RM expects keys to
  1115	 * have only one specific type.
  1116	 */
> 1117	struct registry_list_entry {
  1118		struct list_head head;
  1119		enum registry_type type;
  1120		size_t klen;
  1121		char key[REGISTRY_MAX_KEY_LENGTH];
  1122		size_t vlen;
  1123		u32 dword;			/* TYPE_DWORD */
  1124		u8 binary[] __counted_by(vlen);	/* TYPE_BINARY or TYPE_STRING */
  1125	};
  1126	

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ