All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Timur Tabi <ttabi@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
	Danilo Krummrich <dakr@redhat.com>
Subject: [drm-misc:for-linux-next 1/1] drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:1117: warning: cannot understand function prototype: 'struct registry_list_entry '
Date: Sat, 27 Apr 2024 10:55:02 +0800	[thread overview]
Message-ID: <202404271044.gYbO4F1B-lkp@intel.com> (raw)

tree:   git://anongit.freedesktop.org/drm/drm-misc for-linux-next
head:   61ba791c4a7a09a370c45b70a81b8c7d4cf6b2ae
commit: b58a0bc904ffa091fc020f7fd00e91808fec820e [1/1] nouveau: add command-line GSP-RM registry support
config: parisc-defconfig (https://download.01.org/0day-ci/archive/20240427/202404271044.gYbO4F1B-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240427/202404271044.gYbO4F1B-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/202404271044.gYbO4F1B-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

                 reply	other threads:[~2024-04-27  2:55 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=202404271044.gYbO4F1B-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dakr@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ttabi@nvidia.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 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.