From: Sean Christopherson <seanjc@google.com>
To: Cun Li <cun.jia.li@gmail.com>
Cc: vkuznets@redhat.com, pbonzini@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: update depracated and inappropriate jump label API
Date: Tue, 19 Jan 2021 12:46:13 -0800 [thread overview]
Message-ID: <YAdFFdyMZrTe0SFa@google.com> (raw)
In-Reply-To: <20210116055009.118377-1-cun.jia.li@gmail.com>
s/depracated/deprecated
And maybe reword the shortlog to be more explicit? E.g.
KVM: Stop using deprecated jump label APIs
On Sat, Jan 16, 2021, Cun Li wrote:
> The use of 'struct static_key' and 'static_key_false' is
> deprecated. Use the new API.
>
> mmu_audit_key can only be true or false so it would be nice to use
> static_branch_enable()/static_branch_disable() for it and not
> static_key_slow_inc()/static_key_slow_dec().
Does anyone even build with CONFIG_KVM_MMU_AUDIT=y, let alone actually use the
auditing capabilities?
next prev parent reply other threads:[~2021-01-19 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 15:24 [PATCH] KVM: update depracated jump label API Cun Li
2021-01-11 17:15 ` Vitaly Kuznetsov
2021-01-16 5:41 ` Cun Li
2021-01-16 5:50 ` [PATCH] KVM: update depracated and inappropriate " Cun Li
2021-01-19 20:46 ` Sean Christopherson [this message]
2021-01-26 17:57 ` [PATCH] KVM: update depracated " Paolo Bonzini
2021-01-26 18:51 ` Sean Christopherson
2021-01-13 8:43 ` kernel test robot
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=YAdFFdyMZrTe0SFa@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=cun.jia.li@gmail.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@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 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.