From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Subject: Re: [PATCH v3 3/4] KVM: nVMX: Disallow access to vmcs12 fields that aren't supported by "hardware"
Date: Fri, 9 Jan 2026 18:06:02 +0100 [thread overview]
Message-ID: <202601091810.glHSu2rO-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "high confidence checkpatch report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260109041523.1027323-4-seanjc@google.com>
References: <20260109041523.1027323-4-seanjc@google.com>
TO: Sean Christopherson <seanjc@google.com>
Hi Sean,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 9448598b22c50c8a5bb77a9103e2d49f134c9578]
url: https://github.com/intel-lab-lkp/linux/commits/Sean-Christopherson/KVM-nVMX-Setup-VMX-MSRs-on-loading-CPU-during-nested_vmx_hardware_setup/20260109-122321
base: 9448598b22c50c8a5bb77a9103e2d49f134c9578
patch link: https://lore.kernel.org/r/20260109041523.1027323-4-seanjc%40google.com
patch subject: [PATCH v3 3/4] KVM: nVMX: Disallow access to vmcs12 fields that aren't supported by "hardware"
:::::: branch date: 13 hours ago
:::::: commit date: 13 hours ago
reproduce: (https://download.01.org/0day-ci/archive/20260109/202601091810.glHSu2rO-lkp@intel.com/reproduce)
# many are suggestions rather than must-fix
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Xin Li <xin@zytor.com'
#34:
Reviewed-by: Xin Li <xin@zytor.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-09 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 17:06 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-09 4:15 [PATCH v3 0/4] KVM: nVMX: Disallow access to vmcs12 fields that aren't supported by "hardware" Sean Christopherson
2026-01-09 4:15 ` [PATCH v3 3/4] " Sean Christopherson
2026-01-09 14:08 ` Xiaoyao Li
2026-01-09 14:44 ` Sean Christopherson
2026-01-09 15:17 ` Sean Christopherson
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=202601091810.glHSu2rO-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.