From: kernel test robot <lkp@intel.com>
To: Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, longli@microsoft.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mshv: Add support for integrated scheduler
Date: Fri, 30 Jan 2026 17:15:43 +0800 [thread overview]
Message-ID: <202601301732.2k4q81GI-lkp@intel.com> (raw)
In-Reply-To: <176971725312.67225.3938191771112866951.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net>
Hi Stanislav,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.19-rc7 next-20260129]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Stanislav-Kinsburskii/mshv-Add-support-for-integrated-scheduler/20260130-041014
base: linus/master
patch link: https://lore.kernel.org/r/176971725312.67225.3938191771112866951.stgit%40skinsburskii-cloud-desktop.internal.cloudapp.net
patch subject: [PATCH v2] mshv: Add support for integrated scheduler
config: x86_64-buildonly-randconfig-004-20260130 (https://download.01.org/0day-ci/archive/20260130/202601301732.2k4q81GI-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260130/202601301732.2k4q81GI-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/202601301732.2k4q81GI-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/hv/mshv_root_main.c:2260:2: error: expected identifier or '('
2260 | dev_dbg(dev, "vmm_caps = %#llx\n", mshv_root.vmm_caps.as_uint64[0]);
| ^
include/linux/dev_printk.h:171:2: note: expanded from macro 'dev_dbg'
171 | dev_no_printk(KERN_DEBUG, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^
include/linux/dev_printk.h:137:3: note: expanded from macro 'dev_no_printk'
137 | ({ \
| ^
>> drivers/hv/mshv_root_main.c:2260:2: error: expected ')'
include/linux/dev_printk.h:171:2: note: expanded from macro 'dev_dbg'
171 | dev_no_printk(KERN_DEBUG, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^
include/linux/dev_printk.h:137:3: note: expanded from macro 'dev_no_printk'
137 | ({ \
| ^
drivers/hv/mshv_root_main.c:2260:2: note: to match this '('
include/linux/dev_printk.h:171:2: note: expanded from macro 'dev_dbg'
171 | dev_no_printk(KERN_DEBUG, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^
include/linux/dev_printk.h:137:2: note: expanded from macro 'dev_no_printk'
137 | ({ \
| ^
drivers/hv/mshv_root_main.c:2262:2: error: expected identifier or '('
2262 | return 0;
| ^
>> drivers/hv/mshv_root_main.c:2263:1: error: extraneous closing brace ('}')
2263 | }
| ^
4 errors generated.
vim +2260 drivers/hv/mshv_root_main.c
621191d709b148 Nuno Das Neves 2025-03-14 2246
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2247 static int __init mshv_init_vmm_caps(struct device *dev)
fd612d97a458f0 Purna Pavan Chandra Aekkaladevi 2025-10-10 2248 {
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2249 int ret;
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2250
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2251 ret = hv_call_get_partition_property_ex(HV_PARTITION_ID_SELF,
fd612d97a458f0 Purna Pavan Chandra Aekkaladevi 2025-10-10 2252 HV_PARTITION_PROPERTY_VMM_CAPABILITIES,
fd612d97a458f0 Purna Pavan Chandra Aekkaladevi 2025-10-10 2253 0, &mshv_root.vmm_caps,
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2254 sizeof(mshv_root.vmm_caps));
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2255 if (ret && hv_l1vh_partition())
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2256 dev_err(dev, "Failed to get VMM capabilities: %d\n", ret);
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2257 return ret;
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2258 }
fd612d97a458f0 Purna Pavan Chandra Aekkaladevi 2025-10-10 2259
fd612d97a458f0 Purna Pavan Chandra Aekkaladevi 2025-10-10 @2260 dev_dbg(dev, "vmm_caps = %#llx\n", mshv_root.vmm_caps.as_uint64[0]);
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2261
21480aa03ff5bc Stanislav Kinsburskii 2026-01-29 2262 return 0;
fd612d97a458f0 Purna Pavan Chandra Aekkaladevi 2025-10-10 @2263 }
fd612d97a458f0 Purna Pavan Chandra Aekkaladevi 2025-10-10 2264
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-30 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 20:07 [PATCH v2] mshv: Add support for integrated scheduler Stanislav Kinsburskii
2026-01-30 1:29 ` Michael Kelley
2026-01-30 5:51 ` kernel test robot
2026-01-30 9:15 ` kernel test robot [this message]
2026-01-30 15:09 ` kernel test robot
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=202601301732.2k4q81GI-lkp@intel.com \
--to=lkp@intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longli@microsoft.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skinsburskii@linux.microsoft.com \
--cc=wei.liu@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox