From: kernel test robot <lkp@intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [davidhildenbrand:balloon 2/23] drivers/misc/vmw_balloon.c:1857:9: error: 'b' undeclared; did you mean 'mb'?
Date: Sun, 19 Oct 2025 01:19:15 +0800 [thread overview]
Message-ID: <202510190152.ddbXDK88-lkp@intel.com> (raw)
tree: https://github.com/davidhildenbrand/linux balloon
head: 7eef08e97c0bed3ecf03a02e2283be82b9bce389
commit: 754bcc13125987809bf134f12b7d8db0bf74934c [2/23] vmw_balloon: remove vmballoon_compaction_init()
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20251019/202510190152.ddbXDK88-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251019/202510190152.ddbXDK88-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/202510190152.ddbXDK88-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/misc/vmw_balloon.c: In function 'vmballoon_init':
>> drivers/misc/vmw_balloon.c:1857:9: error: 'b' undeclared (first use in this function); did you mean 'mb'?
1857 | b->b_dev_info.migratepage = vmballoon_migratepage;
| ^
| mb
drivers/misc/vmw_balloon.c:1857:9: note: each undeclared identifier is reported only once for each function it appears in
vim +1857 drivers/misc/vmw_balloon.c
1837
1838 static int __init vmballoon_init(void)
1839 {
1840 int error;
1841
1842 /*
1843 * Check if we are running on VMware's hypervisor and bail out
1844 * if we are not.
1845 */
1846 if (x86_hyper_type != X86_HYPER_VMWARE)
1847 return -ENODEV;
1848
1849 INIT_DELAYED_WORK(&balloon.dwork, vmballoon_work);
1850
1851 error = vmballoon_register_shrinker(&balloon);
1852 if (error)
1853 return error;
1854
1855 balloon_devinfo_init(&balloon.b_dev_info);
1856 #ifdef CONFIG_BALLOON_COMPACTION
> 1857 b->b_dev_info.migratepage = vmballoon_migratepage;
1858 #endif /* CONFIG_BALLOON_COMPACTION */
1859
1860 INIT_LIST_HEAD(&balloon.huge_pages);
1861 spin_lock_init(&balloon.comm_lock);
1862 init_rwsem(&balloon.conf_sem);
1863 balloon.vmci_doorbell = VMCI_INVALID_HANDLE;
1864 balloon.batch_page = NULL;
1865 balloon.page = NULL;
1866 balloon.reset_required = true;
1867
1868 queue_delayed_work(system_freezable_wq, &balloon.dwork, 0);
1869
1870 vmballoon_debugfs_init(&balloon);
1871
1872 return 0;
1873 }
1874
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-10-18 17:19 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=202510190152.ddbXDK88-lkp@intel.com \
--to=lkp@intel.com \
--cc=david@redhat.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.