From: Paul Durrant <paul.durrant@citrix.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org,
xen-devel@lists.xenproject.org
Cc: Paul Durrant <paul.durrant@citrix.com>,
Anthony Perard <anthony.perard@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH v9 17/18] MAINTAINERS: add myself as a Xen maintainer
Date: Tue, 8 Jan 2019 14:49:02 +0000 [thread overview]
Message-ID: <20190108144903.8249-18-paul.durrant@citrix.com> (raw)
In-Reply-To: <20190108144903.8249-1-paul.durrant@citrix.com>
I have made many significant contributions to the Xen code in QEMU,
particularly the recent patches introducing a new PV device framework.
I intend to make further significant contributions, porting other PV back-
ends to the new framework with the intent of eventually removing the
legacy code. It therefore seems reasonable that I become a maintainer of
the Xen code.
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Acked-by: Anthony Perard <anthony.perard@citrix.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
---
Cc: Paolo Bonzini <pbonzini@redhat.com>
v2:
- Fix typo
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index aeac96401d..02df9765df 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -407,6 +407,7 @@ Guest CPU Cores (Xen):
X86
M: Stefano Stabellini <sstabellini@kernel.org>
M: Anthony Perard <anthony.perard@citrix.com>
+M: Paul Durrant <paul.durrant@citrix.com>
L: xen-devel@lists.xenproject.org
S: Supported
F: */xen*
--
2.20.1.2.gb21ebb6
next prev parent reply other threads:[~2019-01-08 14:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 14:48 [Qemu-devel] [PATCH v9 00/18] Xen PV backend 'qdevification' Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 01/18] xen: re-name XenDevice to XenLegacyDevice Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 02/18] xen: introduce new 'XenBus' and 'XenDevice' object hierarchy Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 03/18] xen: introduce 'xen-block', 'xen-disk' and 'xen-cdrom' Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 04/18] xen: create xenstore areas for XenDevice-s Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 05/18] xen: add xenstore watcher infrastructure Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 06/18] xen: add grant table interface for XenDevice-s Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 07/18] xen: add event channel " Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 08/18] xen: duplicate xen_disk.c as basis of dataplane/xen-block.c Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 09/18] xen: remove unnecessary code from dataplane/xen-block.c Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 10/18] xen: add header and build dataplane/xen-block.c Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 11/18] xen: remove 'XenBlkDev' and 'blkdev' names from dataplane/xen-block Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 12/18] xen: remove 'ioreq' struct/varable/field names from dataplane/xen-block.c Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 13/18] xen: purge 'blk' and 'ioreq' from function names in dataplane/xen-block.c Paul Durrant
2019-01-08 14:48 ` [Qemu-devel] [PATCH v9 14/18] xen: add implementations of xen-block connect and disconnect functions Paul Durrant
2019-01-08 14:49 ` [Qemu-devel] [PATCH v9 15/18] xen: add a mechanism to automatically create XenDevice-s Paul Durrant
2019-01-08 14:49 ` [Qemu-devel] [PATCH v9 16/18] xen: automatically create XenBlockDevice-s Paul Durrant
2019-01-09 12:09 ` Anthony PERARD
2019-01-09 12:30 ` Paul Durrant
2019-01-08 14:49 ` Paul Durrant [this message]
2019-01-08 14:49 ` [Qemu-devel] [PATCH v9 18/18] xen: remove the legacy 'xen_disk' backend Paul Durrant
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=20190108144903.8249-18-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 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).