From: Sean Christopherson <seanjc@google.com>
To: David Matlack <dmatlack@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] KVM: x86/mmu: Make @tdp_mmu_allowed static
Date: Wed, 15 Feb 2023 16:44:47 -0800 [thread overview]
Message-ID: <Y+18f7go7J98XbzR@google.com> (raw)
In-Reply-To: <20230213212844.3062733-1-dmatlack@google.com>
On Mon, Feb 13, 2023, David Matlack wrote:
> Make @tdp_mmu_allowed static since it is only ever used within
Doesn't "@" usually refer to function parameters?
> arch/x86/kvm/mmu/mmu.c.
>
> Link: https://lore.kernel.org/kvm/202302072055.odjDVd5V-lkp@intel.com/
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: David Matlack <dmatlack@google.com>
> ---
Fixes: 3af15ff47c4d ("KVM: x86/mmu: Change tdp_mmu to a read-only parameter")
Reviewed-by: Sean Christopherson <seanjc@google.com>
Paolo, want to grab this one directly for 6.3?
next prev parent reply other threads:[~2023-02-16 0:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 21:28 [PATCH] KVM: x86/mmu: Make @tdp_mmu_allowed static David Matlack
2023-02-16 0:44 ` Sean Christopherson [this message]
2023-02-16 1:06 ` David Matlack
2023-02-16 15:35 ` Sean Christopherson
2023-02-16 17:29 ` Paolo Bonzini
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=Y+18f7go7J98XbzR@google.com \
--to=seanjc@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).