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-desktop 36/36] drivers/virt/gunyah/rsc_mgr.c:162: warning: Function parameter or struct member 'pm_nb' not described in 'gunyah_rm'
Date: Tue, 24 Mar 2026 21:04:31 +0800 [thread overview]
Message-ID: <202603242012.8jAkuvin-lkp@intel.com> (raw)
Hi Hrishabh,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12-desktop
head: 2d13a0e00b4d9cf3601b0e0d2c1838ec962f4e88
commit: 7d9fe864dc6289d8c10246453b0c7d3cb3f983f6 [36/36] ANDROID: virt: gunyah: Fetch fresh Gunyah information after restore
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260324/202603242012.8jAkuvin-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/20260324/202603242012.8jAkuvin-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/202603242012.8jAkuvin-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/virt/gunyah/rsc_mgr.c:126: warning: Excess struct member 'ret' description in 'gunyah_rm_message'
drivers/virt/gunyah/rsc_mgr.c:162: warning: Function parameter or struct member 'adev' not described in 'gunyah_rm'
>> drivers/virt/gunyah/rsc_mgr.c:162: warning: Function parameter or struct member 'pm_nb' not described in 'gunyah_rm'
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 +162 drivers/virt/gunyah/rsc_mgr.c
4c11c572f413d00 Elliot Berman 2024-02-22 127
4c11c572f413d00 Elliot Berman 2024-02-22 128 /**
4c11c572f413d00 Elliot Berman 2024-02-22 129 * struct gunyah_rm - private data for communicating w/Gunyah resource manager
4c11c572f413d00 Elliot Berman 2024-02-22 130 * @tx_ghrsc: message queue resource to TX to RM
4c11c572f413d00 Elliot Berman 2024-02-22 131 * @rx_ghrsc: message queue resource to RX from RM
4c11c572f413d00 Elliot Berman 2024-02-22 132 * @active_rx_message: ongoing gunyah_rm_message for which we're receiving fragments
4c11c572f413d00 Elliot Berman 2024-02-22 133 * @call_xarray: xarray to allocate & lookup sequence IDs for Request/Response flows
4c11c572f413d00 Elliot Berman 2024-02-22 134 * @next_seq: next ID to allocate (for xa_alloc_cyclic)
4c11c572f413d00 Elliot Berman 2024-02-22 135 * @recv_msg: cached allocation for Rx messages
4c11c572f413d00 Elliot Berman 2024-02-22 136 * @send_msg: cached allocation for Tx messages. Must hold @send_lock to manipulate.
4c11c572f413d00 Elliot Berman 2024-02-22 137 * @send_lock: synchronization to allow only one request to be sent at a time
4c11c572f413d00 Elliot Berman 2024-02-22 138 * @send_ready: completed when we know Tx message queue can take more messages
4c11c572f413d00 Elliot Berman 2024-02-22 139 * @nh: notifier chain for clients interested in RM notification messages
b387fa408e4054a Elliot Berman 2024-02-22 140 * @miscdev: /dev/gunyah
9281f214814eb6f Elliot Berman 2024-02-22 141 * @parent_fwnode: Parent IRQ fwnode to translate Gunyah hwirqs to Linux irqs
4c11c572f413d00 Elliot Berman 2024-02-22 142 */
4c11c572f413d00 Elliot Berman 2024-02-22 143 struct gunyah_rm {
4c11c572f413d00 Elliot Berman 2024-02-22 144 struct gunyah_resource tx_ghrsc;
4c11c572f413d00 Elliot Berman 2024-02-22 145 struct gunyah_resource rx_ghrsc;
4c11c572f413d00 Elliot Berman 2024-02-22 146 struct gunyah_rm_message *active_rx_message;
4c11c572f413d00 Elliot Berman 2024-02-22 147
4c11c572f413d00 Elliot Berman 2024-02-22 148 struct xarray call_xarray;
4c11c572f413d00 Elliot Berman 2024-02-22 149 u32 next_seq;
4c11c572f413d00 Elliot Berman 2024-02-22 150
4c11c572f413d00 Elliot Berman 2024-02-22 151 unsigned char recv_msg[GUNYAH_RM_MSGQ_MSG_SIZE];
4c11c572f413d00 Elliot Berman 2024-02-22 152 unsigned char send_msg[GUNYAH_RM_MSGQ_MSG_SIZE];
4c11c572f413d00 Elliot Berman 2024-02-22 153 struct mutex send_lock;
4c11c572f413d00 Elliot Berman 2024-02-22 154 struct completion send_ready;
4c11c572f413d00 Elliot Berman 2024-02-22 155 struct blocking_notifier_head nh;
b387fa408e4054a Elliot Berman 2024-02-22 156
8c11dcc79b79d48 Sreenad Menon 2024-05-02 157 struct auxiliary_device adev;
b387fa408e4054a Elliot Berman 2024-02-22 158 struct miscdevice miscdev;
9281f214814eb6f Elliot Berman 2024-02-22 159 struct fwnode_handle *parent_fwnode;
7d9fe864dc6289d Hrishabh Rajput 2025-08-13 160
7d9fe864dc6289d Hrishabh Rajput 2025-08-13 161 struct notifier_block pm_nb;
4c11c572f413d00 Elliot Berman 2024-02-22 @162 };
4c11c572f413d00 Elliot Berman 2024-02-22 163
:::::: The code at line 162 was first introduced by commit
:::::: 4c11c572f413d00b06538a5b8c1ab6c5267232ea FROMLIST: gunyah: rsc_mgr: Add resource manager RPC core
:::::: TO: Elliot Berman <quic_eberman@quicinc.com>
:::::: CC: Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-24 13:05 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=202603242012.8jAkuvin-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.