From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, cohuck@redhat.com,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <richard.henderson@linaro.org>,
David Hildenbrand <david@redhat.com>
Subject: [Qemu-devel] [PATCH v1 1/5] MAINTAINERS: use KVM s390x maintainers for kvm-stubs.c and kvm_s390x.h
Date: Thu, 28 Sep 2017 15:46:05 +0200 [thread overview]
Message-ID: <20170928134609.16985-2-david@redhat.com> (raw)
In-Reply-To: <20170928134609.16985-1-david@redhat.com>
Forgot it when factoring code out into these files. This is 100% s390x
KVM material.
Signed-off-by: David Hildenbrand <david@redhat.com>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 932443df41..772ac209e1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -299,6 +299,8 @@ M: Cornelia Huck <cohuck@redhat.com>
M: Alexander Graf <agraf@suse.de>
S: Maintained
F: target/s390x/kvm.c
+F: target/s390x/kvm_s390x.h
+F: target/s390x/kvm-stub.c
F: target/s390x/ioinst.[ch]
F: target/s390x/machine.c
F: hw/intc/s390_flic.c
--
2.13.5
next prev parent reply other threads:[~2017-09-28 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 13:46 [Qemu-devel] [PATCH v1 0/5] s390x: CPU related cleanups and one fix David Hildenbrand
2017-09-28 13:46 ` David Hildenbrand [this message]
2017-09-28 13:52 ` [Qemu-devel] [PATCH v1 1/5] MAINTAINERS: use KVM s390x maintainers for kvm-stubs.c and kvm_s390x.h Christian Borntraeger
2017-09-28 13:46 ` [Qemu-devel] [PATCH v1 2/5] s390x: raise CPU hotplug irq after really hotplugged David Hildenbrand
2017-09-28 13:46 ` [Qemu-devel] [PATCH v1 3/5] s390x/cpumodel: fix max STFL(E) bit number David Hildenbrand
2017-09-28 13:46 ` [Qemu-devel] [PATCH v1 4/5] target/s390x: get rid of next_core_id David Hildenbrand
2017-09-28 13:46 ` [Qemu-devel] [PATCH v1 5/5] s390x: introduce and use S390_MAX_CPUS David Hildenbrand
2017-09-29 9:13 ` [Qemu-devel] [PATCH v1 0/5] s390x: CPU related cleanups and one fix Cornelia Huck
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=20170928134609.16985-2-david@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@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).