linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commits in the kvm tree
Date: Fri, 20 Aug 2021 08:21:47 +1000	[thread overview]
Message-ID: <20210820082147.5fcc36b8@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

Hi all,

Commits

  5ac66856417a ("KVM: SVM: AVIC: drop unsupported AVIC base relocation code")
  6b0f5cfa6207 ("KVM: SVM: call avic_vcpu_load/avic_vcpu_put when enabling/disabling AVIC")
  28471728a851 ("KVM: SVM: move check for kvm_vcpu_apicv_active outside of avic_vcpu_{put|load}")
  5f3c6f56ad99 ("KVM: SVM: avoid refreshing avic if its state didn't change")
  2c8c05f69ac3 ("KVM: SVM: remove svm_toggle_avic_for_irq_window")
  11d9e063e484 ("KVM: x86: hyper-v: Deactivate APICv only when AutoEOI feature is in use")
  46cd27246e22 ("KVM: SVM: add warning for mistmatch between AVIC vcpu state and AVIC inhibition")
  626fcb4e640e ("KVM: x86: APICv: fix race in kvm_request_apicv_update on SVM")
  049e1cd8365e ("KVM: x86: don't disable APICv memslot when inhibited")
  6ca19df1ae70 ("KVM: x86/mmu: allow APICv memslot to be enabled but invisible")
  359a029cf50e ("KVM: x86/mmu: allow kvm_faultin_pfn to return page fault handling code")
  d67c15c4ac94 ("KVM: x86/mmu: rename try_async_pf to kvm_faultin_pfn")
  b04260e0857d ("KVM: x86/mmu: bump mmu notifier count in kvm_zap_gfn_range")
  7b03fdb9eba6 ("KVM: x86/mmu: add comment explaining arguments to kvm_zap_gfn_range")
  cb3b2438457d ("KVM: x86/mmu: fix parameters to kvm_flush_remote_tlbs_with_address")
  175c4f82f59f ("Revert "KVM: x86/mmu: Allow zap gfn range to operate under the mmu read lock"")

are missing a Signed-off-by from their committer.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-08-19 22:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 22:21 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-22  0:52 linux-next: Signed-off-by missing for commits in the kvm tree Stephen Rothwell
2021-06-24 21:58 Stephen Rothwell
2021-06-24 22:03 ` Paolo Bonzini
2018-03-18 13:44 Stephen Rothwell
2017-12-14 20:26 Stephen Rothwell
2017-11-18 14:11 Stephen Rothwell

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=20210820082147.5fcc36b8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).