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 commit in the kvm tree
Date: Fri, 17 Dec 2021 05:52:46 +1100 [thread overview]
Message-ID: <20211217055246.2e5fdf11@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2581 bytes --]
Hi all,
Commits
244893fa2859 ("KVM: Dynamically allocate "new" memslots from the get-go")
0f9bdef3d933 ("KVM: Wait 'til the bitter end to initialize the "new" memslot")
44401a204734 ("KVM: Optimize overlapping memslots check")
f4209439b522 ("KVM: Optimize gfn lookup in kvm_zap_gfn_range()")
bcb63dcde829 ("KVM: Call kvm_arch_flush_shadow_memslot() on the old slot in kvm_invalidate_memslot()")
a54d806688fe ("KVM: Keep memslots in tree-based structures instead of array-based ones")
6a656832aa75 ("KVM: s390: Introduce kvm_s390_get_gfn_end()")
ed922739c919 ("KVM: Use interval tree to do fast hva lookup in memslots")
26b8345abc75 ("KVM: Resolve memslot ID via a hash table instead of via a static array")
1e8617d37fc3 ("KVM: Move WARN on invalid memslot index to update_memslots()")
c928bfc2632f ("KVM: Integrate gfn_to_memslot_approx() into search_memslots()")
f5756029eef5 ("KVM: x86: Use nr_memslot_pages to avoid traversing the memslots array")
e0c2b6338ac8 ("KVM: x86: Don't call kvm_mmu_change_mmu_pages() if the count hasn't changed")
7cd08553ab10 ("KVM: Don't make a full copy of the old memslot in __kvm_set_memory_region()")
ec5c86976674 ("KVM: s390: Skip gfn/size sanity checks on memslot DELETE or FLAGS_ONLY")
77aedf26fe5d ("KVM: x86: Don't assume old/new memslots are non-NULL at memslot commit")
07921665a651 ("KVM: Use prepare/commit hooks to handle generic memslot metadata updates")
6a99c6e3f52a ("KVM: Stop passing kvm_userspace_memory_region to arch memslot hooks")
d01495d4cffb ("KVM: RISC-V: Use "new" memslot instead of userspace memory region")
9d7d18ee3f48 ("KVM: x86: Use "new" memslot instead of userspace memory region")
cf5b486922dc ("KVM: s390: Use "new" memslot instead of userspace memory region")
eaaaed137ecc ("KVM: PPC: Avoid referencing userspace memory region in memslot updates")
3b1816177bfe ("KVM: MIPS: Drop pr_debug from memslot commit to avoid using "mem"")
509c594ca2dc ("KVM: arm64: Use "new" memslot instead of userspace memory region")
537a17b31493 ("KVM: Let/force architectures to deal with arch specific memslot data")
ce5f0215620c ("KVM: Use "new" memslot's address space ID instead of dedicated param")
4e4d30cb9b87 ("KVM: Resync only arch fields when slots_arch_lock gets reacquired")
47ea7d900b1c ("KVM: Open code kvm_delete_memslot() into its only caller")
afa319a54a8c ("KVM: Require total number of memslot pages to fit in an unsigned long")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-12-16 18:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 18:52 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-23 22:33 linux-next: Signed-off-by missing for commit in the kvm tree Stephen Rothwell
2022-05-22 0:51 Stephen Rothwell
2022-03-21 13:07 Stephen Rothwell
2022-01-08 7:24 Stephen Rothwell
2021-09-30 22:42 Stephen Rothwell
2021-02-04 20:18 Stephen Rothwell
2021-02-05 14:36 ` Joao Martins
2020-08-04 22:29 Stephen Rothwell
2020-06-11 1:04 Stephen Rothwell
2020-04-20 22:32 Stephen Rothwell
2020-04-19 22:26 Stephen Rothwell
2020-01-23 20:43 Stephen Rothwell
2018-12-21 13:57 Stephen Rothwell
2018-08-06 21:39 Stephen Rothwell
2018-08-06 21:55 ` Paolo Bonzini
2017-08-10 23:28 Stephen Rothwell
2017-08-11 6:29 ` David Hildenbrand
2017-08-11 12:36 ` Radim Krčmář
2017-08-11 14:01 ` 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=20211217055246.2e5fdf11@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pbonzini@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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