From: Tamas K Lengyel <tlengyel@novetta.com>
To: xen-devel@lists.xen.org
Cc: kevin.tian@intel.com, wei.liu2@citrix.com,
ian.campbell@citrix.com, rcojocaru@bitdefender.com,
stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
eddie.dong@intel.com, jbeulich@suse.com, jun.nakajima@intel.com,
andrew.cooper3@citrix.com, Tamas K Lengyel <tlengyel@novetta.com>,
keir@xen.org
Subject: [PATCH v5 4/4] MAINTAINERS: support for xen-access
Date: Thu, 9 Jul 2015 09:14:16 -0400 [thread overview]
Message-ID: <1436447656-16334-4-git-send-email-tlengyel@novetta.com> (raw)
In-Reply-To: <1436447656-16334-1-git-send-email-tlengyel@novetta.com>
Add tools/tests/xen-acess to the supported list under VM EVENT/MEM ACCESS.
Signed-off-by: Tamas K Lengyel <tlengyel@novetta.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1e74688..dae0aa3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -389,6 +389,7 @@ F: xen/common/mem_access.c
F: xen/arch/x86/hvm/event.c
F: xen/arch/x86/monitor.c
F: xen/arch/x86/vm_event.c
+F: tools/tests/xen-access
XENTRACE
M: George Dunlap <george.dunlap@eu.citrix.com>
--
2.1.4
next prev parent reply other threads:[~2015-07-09 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 13:14 [PATCH v5 1/4] x86/monitor: add get_capabilities to monitor_op domctl Tamas K Lengyel
2015-07-09 13:14 ` [PATCH v5 2/4] x86/vm_event: toggle singlestep from vm_event response Tamas K Lengyel
2015-07-10 10:30 ` Jan Beulich
2015-07-10 11:36 ` Ian Campbell
2015-07-10 14:33 ` Lengyel, Tamas
2015-07-09 13:14 ` [PATCH v5 3/4] x86/monitor: don't use hvm_funcs directly Tamas K Lengyel
2015-07-09 13:20 ` Razvan Cojocaru
2015-07-09 13:14 ` Tamas K Lengyel [this message]
2015-07-09 13:17 ` [PATCH v5 4/4] MAINTAINERS: support for xen-access Razvan Cojocaru
2015-07-09 13:50 ` Lengyel, Tamas
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=1436447656-16334-4-git-send-email-tlengyel@novetta.com \
--to=tlengyel@novetta.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.