From: Sean Christopherson <sean.j.christopherson@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org,
Robert Hu <robert.hu@intel.com>,
Farrah Chen <farrah.chen@intel.com>,
Danmei Wei <danmei.wei@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RFC PATCH kvm] KVM: VMX: vmx_uret_msrs_list[] can be static
Date: Tue, 29 Sep 2020 17:17:49 -0700 [thread overview]
Message-ID: <20200930001749.GF32531@linux.intel.com> (raw)
In-Reply-To: <20200928153714.GA6285@a3a878002045>
On Mon, Sep 28, 2020 at 11:37:14PM +0800, kernel test robot wrote:
>
> Fixes: 14a61b642de9 ("KVM: VMX: Rename "vmx_msr_index" to "vmx_uret_msrs_list"")
> Signed-off-by: kernel test robot <lkp@intel.com>
> ---
Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH kvm] KVM: VMX: vmx_uret_msrs_list[] can be static
Date: Tue, 29 Sep 2020 17:17:49 -0700 [thread overview]
Message-ID: <20200930001749.GF32531@linux.intel.com> (raw)
In-Reply-To: <20200928153714.GA6285@a3a878002045>
[-- Attachment #1: Type: text/plain, Size: 283 bytes --]
On Mon, Sep 28, 2020 at 11:37:14PM +0800, kernel test robot wrote:
>
> Fixes: 14a61b642de9 ("KVM: VMX: Rename "vmx_msr_index" to "vmx_uret_msrs_list"")
> Signed-off-by: kernel test robot <lkp@intel.com>
> ---
Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
next prev parent reply other threads:[~2020-09-30 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 15:37 [kvm:queue 136/148] arch/x86/kvm/vmx/vmx.c:440:11: sparse: sparse: symbol 'vmx_uret_msrs_list' was not declared. Should it be kernel test robot
2020-09-28 15:37 ` [RFC PATCH kvm] KVM: VMX: vmx_uret_msrs_list[] can be static kernel test robot
2020-09-28 15:37 ` kernel test robot
2020-09-30 0:17 ` Sean Christopherson [this message]
2020-09-30 0: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=20200930001749.GF32531@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=danmei.wei@intel.com \
--cc=farrah.chen@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pbonzini@redhat.com \
--cc=robert.hu@intel.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.