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: 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 23:09:39 +0800 [thread overview]
Message-ID: <202601302238.nUbp7p58-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-randconfig-002-20260130 (https://download.01.org/0day-ci/archive/20260130/202601302238.nUbp7p58-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/20260130/202601302238.nUbp7p58-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/202601302238.nUbp7p58-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/hv/mshv_root_main.c: In function 'mshv_init_vmm_caps':
drivers/hv/mshv_root_main.c:2255:9: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
2255 | if (ret && hv_l1vh_partition())
| ^~
drivers/hv/mshv_root_main.c:2257:17: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if'
2257 | return ret;
| ^~~~~~
In file included from include/linux/device.h:15,
from include/linux/blk_types.h:11,
from include/linux/writeback.h:13,
from include/linux/memcontrol.h:23,
from include/linux/resume_user_mode.h:8,
from include/linux/entry-virt.h:6,
from drivers/hv/mshv_root_main.c:11:
drivers/hv/mshv_root_main.c: At top level:
>> include/linux/dev_printk.h:137:10: error: expected identifier or '(' before '{' token
137 | ({ \
| ^
include/linux/dev_printk.h:171:9: note: in expansion of macro 'dev_no_printk'
171 | dev_no_printk(KERN_DEBUG, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~~~~~~~
drivers/hv/mshv_root_main.c:2260:9: note: in expansion of macro 'dev_dbg'
2260 | dev_dbg(dev, "vmm_caps = %#llx\n", mshv_root.vmm_caps.as_uint64[0]);
| ^~~~~~~
drivers/hv/mshv_root_main.c:2262:9: error: expected identifier or '(' before 'return'
2262 | return 0;
| ^~~~~~
drivers/hv/mshv_root_main.c:2263:1: error: expected identifier or '(' before '}' token
2263 | }
| ^
vim +137 include/linux/dev_printk.h
af628aae8640c26 Greg Kroah-Hartman 2019-12-09 99
ad7d61f159db739 Chris Down 2021-06-15 100 /*
ad7d61f159db739 Chris Down 2021-06-15 101 * Need to take variadic arguments even though we don't use them, as dev_fmt()
ad7d61f159db739 Chris Down 2021-06-15 102 * may only just have been expanded and may result in multiple arguments.
ad7d61f159db739 Chris Down 2021-06-15 103 */
ad7d61f159db739 Chris Down 2021-06-15 104 #define dev_printk_index_emit(level, fmt, ...) \
ad7d61f159db739 Chris Down 2021-06-15 105 printk_index_subsys_emit("%s %s: ", level, fmt)
ad7d61f159db739 Chris Down 2021-06-15 106
ad7d61f159db739 Chris Down 2021-06-15 107 #define dev_printk_index_wrap(_p_func, level, dev, fmt, ...) \
ad7d61f159db739 Chris Down 2021-06-15 108 ({ \
ad7d61f159db739 Chris Down 2021-06-15 109 dev_printk_index_emit(level, fmt); \
ad7d61f159db739 Chris Down 2021-06-15 110 _p_func(dev, fmt, ##__VA_ARGS__); \
ad7d61f159db739 Chris Down 2021-06-15 111 })
ad7d61f159db739 Chris Down 2021-06-15 112
ad7d61f159db739 Chris Down 2021-06-15 113 /*
ad7d61f159db739 Chris Down 2021-06-15 114 * Some callsites directly call dev_printk rather than going through the
ad7d61f159db739 Chris Down 2021-06-15 115 * dev_<level> infrastructure, so we need to emit here as well as inside those
ad7d61f159db739 Chris Down 2021-06-15 116 * level-specific macros. Only one index entry will be produced, either way,
ad7d61f159db739 Chris Down 2021-06-15 117 * since dev_printk's `fmt` isn't known at compile time if going through the
ad7d61f159db739 Chris Down 2021-06-15 118 * dev_<level> macros.
ad7d61f159db739 Chris Down 2021-06-15 119 *
ad7d61f159db739 Chris Down 2021-06-15 120 * dev_fmt() isn't called for dev_printk when used directly, as it's used by
ad7d61f159db739 Chris Down 2021-06-15 121 * the dev_<level> macros internally which already have dev_fmt() processed.
ad7d61f159db739 Chris Down 2021-06-15 122 *
ad7d61f159db739 Chris Down 2021-06-15 123 * We also can't use dev_printk_index_wrap directly, because we have a separate
ad7d61f159db739 Chris Down 2021-06-15 124 * level to process.
ad7d61f159db739 Chris Down 2021-06-15 125 */
ad7d61f159db739 Chris Down 2021-06-15 126 #define dev_printk(level, dev, fmt, ...) \
ad7d61f159db739 Chris Down 2021-06-15 127 ({ \
ad7d61f159db739 Chris Down 2021-06-15 128 dev_printk_index_emit(level, fmt); \
ad7d61f159db739 Chris Down 2021-06-15 129 _dev_printk(level, dev, fmt, ##__VA_ARGS__); \
ad7d61f159db739 Chris Down 2021-06-15 130 })
ad7d61f159db739 Chris Down 2021-06-15 131
c26ec799042a388 Geert Uytterhoeven 2024-02-28 132 /*
c26ec799042a388 Geert Uytterhoeven 2024-02-28 133 * Dummy dev_printk for disabled debugging statements to use whilst maintaining
c26ec799042a388 Geert Uytterhoeven 2024-02-28 134 * gcc's format checking.
c26ec799042a388 Geert Uytterhoeven 2024-02-28 135 */
c26ec799042a388 Geert Uytterhoeven 2024-02-28 136 #define dev_no_printk(level, dev, fmt, ...) \
c26ec799042a388 Geert Uytterhoeven 2024-02-28 @137 ({ \
c26ec799042a388 Geert Uytterhoeven 2024-02-28 138 if (0) \
c26ec799042a388 Geert Uytterhoeven 2024-02-28 139 _dev_printk(level, dev, fmt, ##__VA_ARGS__); \
c26ec799042a388 Geert Uytterhoeven 2024-02-28 140 })
c26ec799042a388 Geert Uytterhoeven 2024-02-28 141
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-01-30 15:10 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
2026-01-30 15:09 ` kernel test robot [this message]
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=202601302238.nUbp7p58-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=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