From: Sean Christopherson <seanjc@google.com>
To: kernel test robot <lkp@intel.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: Re: [linux-next:master 5175/8213] arch/x86/kvm/vmx/hyperv_evmcs.h:133:30: sparse: sparse: cast truncates bits from constant value (1b009b becomes 9b)
Date: Mon, 18 Dec 2023 07:06:53 -0800 [thread overview]
Message-ID: <ZYBgDTkt_tZVbfnx@google.com> (raw)
In-Reply-To: <202312171230.oCaBKFUr-lkp@intel.com>
On Sun, Dec 17, 2023, kernel test robot wrote:
> Hi Vitaly,
>
> FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 17cb8a20bde66a520a2ca7aad1063e1ce7382240
> commit: e7ad84db4d718e18c7a133e941ba4c7d4c6d4cbf [5175/8213] KVM: VMX: Split off hyperv_evmcs.{ch}
> config: i386-randconfig-061-20231217 (https://download.01.org/0day-ci/archive/20231217/202312171230.oCaBKFUr-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231217/202312171230.oCaBKFUr-lkp@intel.com/reproduce)
Known shortcoming, just ignore it.
https://lore.kernel.org/all/87v89jmc3q.fsf@redhat.com
next prev parent reply other threads:[~2023-12-18 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 4:13 [linux-next:master 5175/8213] arch/x86/kvm/vmx/hyperv_evmcs.h:133:30: sparse: sparse: cast truncates bits from constant value (1b009b becomes 9b) kernel test robot
2023-12-18 15:06 ` Sean Christopherson [this message]
2023-12-29 14:35 ` Yujie Liu
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=ZYBgDTkt_tZVbfnx@google.com \
--to=seanjc@google.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mlevitsk@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vkuznets@redhat.com \
/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.