From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Sean Christopherson <seanjc@google•com>,
Anup Patel <anup@brainfault•org>
Cc: Aaron Lewis <aaronlewis@google•com>,
Andrew Jones <ajones@ventanamicro•com>,
Haibo Xu <haibo1.xu@intel•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: manual merge of the kvm-x86 tree with the kvm-riscv tree
Date: Tue, 15 Aug 2023 16:32:03 +1000 [thread overview]
Message-ID: <20230815163203.0501fb1d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2386 bytes --]
Hi all,
Today's linux-next merge of the kvm-x86 tree got a conflict in:
tools/testing/selftests/kvm/Makefile
between commits:
17da79e009c3 ("KVM: arm64: selftests: Split get-reg-list test code")
477069398ed6 ("KVM: riscv: selftests: Add get-reg-list test")
from the kvm-riscv tree and commit:
5d1d46f9d56f ("KVM: selftests: Add a selftest for guest prints and formatted asserts")
from the kvm-x86 tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc tools/testing/selftests/kvm/Makefile
index 8852c37fbc2d,77026907968f..000000000000
--- a/tools/testing/selftests/kvm/Makefile
+++ b/tools/testing/selftests/kvm/Makefile
@@@ -151,7 -154,7 +153,8 @@@ TEST_GEN_PROGS_aarch64 += access_tracki
TEST_GEN_PROGS_aarch64 += demand_paging_test
TEST_GEN_PROGS_aarch64 += dirty_log_test
TEST_GEN_PROGS_aarch64 += dirty_log_perf_test
+TEST_GEN_PROGS_aarch64 += get-reg-list
+ TEST_GEN_PROGS_aarch64 += guest_print_test
TEST_GEN_PROGS_aarch64 += kvm_create_max_vcpus
TEST_GEN_PROGS_aarch64 += kvm_page_table_test
TEST_GEN_PROGS_aarch64 += memslot_modification_stress_test
@@@ -166,9 -169,9 +169,10 @@@ TEST_GEN_PROGS_s390x += s390x/reset
TEST_GEN_PROGS_s390x += s390x/sync_regs_test
TEST_GEN_PROGS_s390x += s390x/tprot
TEST_GEN_PROGS_s390x += s390x/cmma_test
+TEST_GEN_PROGS_s390x += s390x/debug_test
TEST_GEN_PROGS_s390x += demand_paging_test
TEST_GEN_PROGS_s390x += dirty_log_test
+ TEST_GEN_PROGS_s390x += guest_print_test
TEST_GEN_PROGS_s390x += kvm_create_max_vcpus
TEST_GEN_PROGS_s390x += kvm_page_table_test
TEST_GEN_PROGS_s390x += rseq_test
@@@ -177,7 -180,7 +181,8 @@@ TEST_GEN_PROGS_s390x += kvm_binary_stat
TEST_GEN_PROGS_riscv += demand_paging_test
TEST_GEN_PROGS_riscv += dirty_log_test
+TEST_GEN_PROGS_riscv += get-reg-list
+ TEST_GEN_PROGS_riscv += guest_print_test
TEST_GEN_PROGS_riscv += kvm_create_max_vcpus
TEST_GEN_PROGS_riscv += kvm_page_table_test
TEST_GEN_PROGS_riscv += set_memory_region_test
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-08-15 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 6:32 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 6:34 linux-next: manual merge of the kvm-x86 tree with the kvm-riscv tree Stephen Rothwell
2024-03-07 3:59 Stephen Rothwell
2026-01-29 15:00 Mark Brown
2026-01-29 15:19 ` Mark Brown
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=20230815163203.0501fb1d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=aaronlewis@google$(echo .)com \
--cc=ajones@ventanamicro$(echo .)com \
--cc=anup@brainfault$(echo .)org \
--cc=haibo1.xu@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=seanjc@google$(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