From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 1/1] drivers/virt/gunyah/rsc_mgr.c:106: warning: Excess struct member 'ret' description in 'gunyah_rm_message'
Date: Fri, 27 Mar 2026 02:38:20 +0800 [thread overview]
Message-ID: <202603270230.vjo9GINA-lkp@intel.com> (raw)
Hi Elliot,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12
head: d73a8ddf419e5ee819fff624cf35bfedd85b5609
commit: 4c11c572f413d00b06538a5b8c1ab6c5267232ea [1/1] FROMLIST: gunyah: rsc_mgr: Add resource manager RPC core
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260327/202603270230.vjo9GINA-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260327/202603270230.vjo9GINA-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/202603270230.vjo9GINA-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/virt/gunyah/rsc_mgr.c:106: warning: Excess struct member 'ret' description in 'gunyah_rm_message'
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for INTEL_MEI_ME
Depends on [n]: X86 && PCI [=y]
Selected by [m]:
- INTEL_MEI_HDCP [=m] && (DRM_I915 [=n] || DRM_XE [=m])
- INTEL_MEI_PXP [=m] && (DRM_I915 [=n] || DRM_XE [=m])
vim +106 drivers/virt/gunyah/rsc_mgr.c
74
75 /**
76 * struct gunyah_rm_message - Represents a complete message from resource manager
77 * @payload: Combined payload of all the fragments (msg headers stripped off).
78 * @size: Size of the payload received so far.
79 * @msg_id: Message ID from the header.
80 * @type: RM_RPC_TYPE_REPLY or RM_RPC_TYPE_NOTIF.
81 * @num_fragments: total number of fragments expected to be received.
82 * @fragments_received: fragments received so far.
83 * @reply: Fields used for request/reply sequences
84 */
85 struct gunyah_rm_message {
86 void *payload;
87 size_t size;
88 u32 msg_id;
89 u8 type;
90
91 u8 num_fragments;
92 u8 fragments_received;
93
94 /**
95 * @ret: Linux return code, there was an error processing message
96 * @seq: Sequence ID for the main message.
97 * @rm_error: For request/reply sequences with standard replies
98 * @seq_done: Signals caller that the RM reply has been received
99 */
100 struct {
101 int ret;
102 u16 seq;
103 enum gunyah_rm_error rm_error;
104 struct completion seq_done;
105 } reply;
> 106 };
107
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-26 18:38 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=202603270230.vjo9GINA-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.