From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-6.1-2025-09 6/6] drivers/virt/gunyah/rsc_mgr.c:194: warning: Function parameter or member 'pm_nb' not described in 'gh_rm'
Date: Sat, 18 Jul 2026 15:52:25 +0800 [thread overview]
Message-ID: <202607181530.sLBbBtSw-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android14-6.1-2025-09
head: 3280cd302df134b0017482f1a83de4325885e4b3
commit: 49a4719b693e7a7d3452677b31a1f32228da3887 [6/6] ANDROID: virt: gunyah: Fetch fresh Gunyah information after restore
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260718/202607181530.sLBbBtSw-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 5c0dfced1adc55429e32b1db08570abd3a219d85)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260718/202607181530.sLBbBtSw-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/202607181530.sLBbBtSw-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/virt/gunyah/rsc_mgr.c:194: warning: Function parameter or member 'adev' not described in 'gh_rm'
>> drivers/virt/gunyah/rsc_mgr.c:194: warning: Function parameter or member 'pm_nb' not described in 'gh_rm'
drivers/virt/gunyah/rsc_mgr.c:669: warning: Function parameter or member '_rm' not described in 'gh_rm_call'
drivers/virt/gunyah/rsc_mgr.c:669: warning: Excess function parameter 'rm' description in 'gh_rm_call'
vim +194 drivers/virt/gunyah/rsc_mgr.c
d5e8df2cc4a170 Elliot Berman 2022-08-10 155
d5e8df2cc4a170 Elliot Berman 2022-08-10 156 /**
d5e8df2cc4a170 Elliot Berman 2022-08-10 157 * struct gh_rm - private data for communicating w/Gunyah resource manager
705a9b5feb1ba9 Elliot Berman 2023-06-12 158 * @dev: pointer to RM platform device
d5e8df2cc4a170 Elliot Berman 2022-08-10 159 * @tx_ghrsc: message queue resource to TX to RM
d5e8df2cc4a170 Elliot Berman 2022-08-10 160 * @rx_ghrsc: message queue resource to RX from RM
9a9fc8d1b2882c Elliot Berman 2023-04-17 161 * @msgq: mailbox instance of TX/RX resources above
9a9fc8d1b2882c Elliot Berman 2023-04-17 162 * @msgq_client: mailbox client of above msgq
d5e8df2cc4a170 Elliot Berman 2022-08-10 163 * @active_rx_connection: ongoing gh_rm_connection for which we're receiving fragments
d5e8df2cc4a170 Elliot Berman 2022-08-10 164 * @last_tx_ret: return value of last mailbox tx
d5e8df2cc4a170 Elliot Berman 2022-08-10 165 * @call_xarray: xarray to allocate & lookup sequence IDs for Request/Response flows
d5e8df2cc4a170 Elliot Berman 2022-08-10 166 * @next_seq: next ID to allocate (for xa_alloc_cyclic)
d5e8df2cc4a170 Elliot Berman 2022-08-10 167 * @cache: cache for allocating Tx messages
d5e8df2cc4a170 Elliot Berman 2022-08-10 168 * @send_lock: synchronization to allow only one request to be sent at a time
d5e8df2cc4a170 Elliot Berman 2022-08-10 169 * @nh: notifier chain for clients interested in RM notification messages
f251362242ba3e Elliot Berman 2022-10-14 170 * @miscdev: /dev/gunyah
4cf9feacb7e4ba Elliot Berman 2022-12-13 171 * @irq_domain: Domain to translate Gunyah hwirqs to Linux irqs
d5e8df2cc4a170 Elliot Berman 2022-08-10 172 */
d5e8df2cc4a170 Elliot Berman 2022-08-10 173 struct gh_rm {
d5e8df2cc4a170 Elliot Berman 2022-08-10 174 struct device *dev;
d5e8df2cc4a170 Elliot Berman 2022-08-10 175 struct gh_resource tx_ghrsc;
d5e8df2cc4a170 Elliot Berman 2022-08-10 176 struct gh_resource rx_ghrsc;
d5e8df2cc4a170 Elliot Berman 2022-08-10 177 struct gh_msgq msgq;
d5e8df2cc4a170 Elliot Berman 2022-08-10 178 struct mbox_client msgq_client;
d5e8df2cc4a170 Elliot Berman 2022-08-10 179 struct gh_rm_connection *active_rx_connection;
d5e8df2cc4a170 Elliot Berman 2022-08-10 180 int last_tx_ret;
d5e8df2cc4a170 Elliot Berman 2022-08-10 181
d5e8df2cc4a170 Elliot Berman 2022-08-10 182 struct xarray call_xarray;
d5e8df2cc4a170 Elliot Berman 2022-08-10 183 u32 next_seq;
d5e8df2cc4a170 Elliot Berman 2022-08-10 184
d5e8df2cc4a170 Elliot Berman 2022-08-10 185 struct kmem_cache *cache;
d5e8df2cc4a170 Elliot Berman 2022-08-10 186 struct mutex send_lock;
d5e8df2cc4a170 Elliot Berman 2022-08-10 187 struct blocking_notifier_head nh;
f251362242ba3e Elliot Berman 2022-10-14 188
1dce9d7d4deea1 Prakruthi Deepak Heragu 2023-02-27 189 struct auxiliary_device adev;
f251362242ba3e Elliot Berman 2022-10-14 190 struct miscdevice miscdev;
4cf9feacb7e4ba Elliot Berman 2022-12-13 191 struct irq_domain *irq_domain;
49a4719b693e7a Hrishabh Rajput 2025-08-13 192
49a4719b693e7a Hrishabh Rajput 2025-08-13 193 struct notifier_block pm_nb;
d5e8df2cc4a170 Elliot Berman 2022-08-10 @194 };
d5e8df2cc4a170 Elliot Berman 2022-08-10 195
:::::: The code at line 194 was first introduced by commit
:::::: d5e8df2cc4a17063dcebc67a939356ad49a665bd FROMLIST: gunyah: rsc_mgr: Add resource manager RPC core
:::::: TO: Elliot Berman <quic_eberman@quicinc.com>
:::::: CC: Aleksei Vetrov <vvvvvv@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-18 7:53 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=202607181530.sLBbBtSw-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.