OpenE2K/qemu-e2k
13
4
Fork 0
Code Issues 4 Pull Requests Projects 2 Releases Activity
9e64f8a3fc
qemu-e2k/MAINTAINERS

868 lines
16 KiB
Plaintext
Raw Normal View History

list of maintainers git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4393 c046a42c-6fe2-441c-8c8c-71466251a162
2008-05-09 11:39:00 +02:00
QEMU Maintainers
================
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
The intention of this file is not to establish who owns what portions of the
code base, but to provide a set of names that developers can consult when they
have a question about a particular subset and also to provide a set of names
to be CC'd when submitting a patch to obtain appropriate review.
update git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4661 c046a42c-6fe2-441c-8c8c-71466251a162
2008-06-04 16:57:43 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
In general, if you have a question about inclusion of a patch, you should
consult qemu-devel and not any specific individual privately.
list of maintainers git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4393 c046a42c-6fe2-441c-8c8c-71466251a162
2008-05-09 11:39:00 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Descriptions of section entries:
M: Mail patches to: FullName <address@domain>
L: Mailing list that is relevant to this area
W: Web-page with status/info
Q: Patchwork web based patch tracking system site
T: SCM tree type and location. Type is one of: git, hg, quilt, stgit.
S: Status, one of the following:
Supported: Someone is actually paid to look after this.
Maintained: Someone actually looks after it.
Odd Fixes: It has a maintainer but they don't have time to do
MAINTAINERS: Delete spurious '.' Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
2011-11-09 20:45:38 +01:00
much other than throw the odd patch in. See below.
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Orphan: No current maintainer [but maybe you could take the
role as you write your new code].
Obsolete: Old code. Something tagged obsolete generally means
it has been replaced by a better system and you
should be using that.
F: Files and directories with wildcard patterns.
A trailing slash includes all files and subdirectory files.
F: drivers/net/ all files in and below drivers/net
F: drivers/net/* all files in drivers/net, but not below
F: */net/* all files in "any top level directory"/net
One pattern per line. Multiple F: lines acceptable.
X: Files and directories that are NOT maintained, same rules as F:
Files exclusions are tested before file matches.
Can be useful for excluding a specific subdirectory, for instance:
F: net/
X: net/ipv6/
matches all files in and below net excluding net/ipv6/
K: Keyword perl extended regex pattern to match content in a
patch or file. For instance:
K: of_get_profile
matches patches or files that contain "of_get_profile"
K: \b(printk|pr_(info|err))\b
matches patches or files that contain one or more of the words
printk, pr_info or pr_err
One regex pattern per line. Multiple K: lines acceptable.
General Project Administration
------------------------------
Change email address My IBM email address will be unaccessible after August 23rd, 2013. Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
2013-08-19 15:49:37 +02:00
M: Anthony Liguori <anthony@codemonkey.ws>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
M: Paul Brook <paul@codesourcery.com>
Guest CPU cores (TCG):
----------------------
Alpha
target-alpha: Claim ownership. I've been maintaining this port for a while now. Signed-off-by: Richard Henderson <rth@twiddle.net>
2011-05-20 21:23:18 +02:00
M: Richard Henderson <rth@twiddle.net>
S: Maintained
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
F: target-alpha/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/alpha/
list of maintainers git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4393 c046a42c-6fe2-441c-8c8c-71466251a162
2008-05-09 11:39:00 +02:00
ARM
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
M: Paul Brook <paul@codesourcery.com>
MAINTAINERS: update maintainer for target-arm and ARM devboards Add myself as co-maintainer alongside Paul Brook for the TCG ARM guest implementation (target-arm) and the ARM dev boards (integratorcp, realview, stellaris, versatilepb). Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Acked-by: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2011-09-20 17:18:46 +02:00
M: Peter Maydell <peter.maydell@linaro.org>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
F: target-arm/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/
F: hw/cpu/a*mpcore.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
CRIS
M: Edgar E. Iglesias <edgar.iglesias@gmail.com>
S: Maintained
F: target-cris/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/cris/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: add LatticeMico32 maintainer Add me as the lm32-target and machines maintainer. Signed-off-by: Michael Walle <michael@walle.cc> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2011-02-17 23:45:18 +01:00
LM32
M: Michael Walle <michael@walle.cc>
S: Maintained
F: target-lm32/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/lm32/
lm32_juart: Relocate and tidy header Signed-off-by: Andreas Färber <afaerber@suse.de>
2013-07-24 22:49:02 +02:00
F: hw/char/lm32_*
MAINTAINERS: add LatticeMico32 maintainer Add me as the lm32-target and machines maintainer. Signed-off-by: Michael Walle <michael@walle.cc> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2011-02-17 23:45:18 +01:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
M68K
M: Paul Brook <paul@codesourcery.com>
MAINTAINERS: Downgrade target-m68k to Odd Fixes m68k patches are not being handled, so let's downgrade to Odd Fixes. Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Paul Brook <paul@codesourcery.com>
2012-04-13 18:30:29 +02:00
S: Odd Fixes
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
F: target-m68k/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/m68k/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MicroBlaze
M: Edgar E. Iglesias <edgar.iglesias@gmail.com>
S: Maintained
F: target-microblaze/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/microblaze/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
list of maintainers git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4393 c046a42c-6fe2-441c-8c8c-71466251a162
2008-05-09 11:39:00 +02:00
MIPS
MAINTAINERS: Change MIPS and SH4 maintainers Since nobody else seems interested in maintaining MIPS and SH4 targets, and as I have done most of the recent code changes, let officialize that. Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2011-01-14 20:39:19 +01:00
M: Aurelien Jarno <aurelien@aurel32.net>
MAINTAINERS: Downgrade target-mips and target-sh4 to Odd Fixes Patches are not being handled, so let's downgrade to Odd Fixes. Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Aurélien Jarno <aurelien@aurel32.net>
2012-04-13 18:33:43 +02:00
S: Odd Fixes
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
F: target-mips/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/mips/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Add top level changes for moxie Signed-off-by: Anthony Green <green@moxielogic.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2013-03-18 20:49:25 +01:00
Moxie
M: Anthony Green <green@moxielogic.com>
S: Maintained
F: target-moxie/
MAINTAINERS: Add myself into MAINTAINERS file Add myself into MAINTAINERS file, I'll looking at target-openrisc and hw/openrisc. Signed-off-by: Jia Liu <proljc@gmail.com> Message-id: 1372769717-852-1-git-send-email-proljc@gmail.com Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-07-02 14:55:17 +02:00
OpenRISC
M: Jia Liu <proljc@gmail.com>
S: Maintained
F: target-openrisc/
F: hw/openrisc/
list of maintainers git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4393 c046a42c-6fe2-441c-8c8c-71466251a162
2008-05-09 11:39:00 +02:00
PowerPC
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
M: Alexander Graf <agraf@suse.de>
MAINTAINERS: Add qemu-ppc to all ppc target stuff Signed-off-by: Andreas Färber <andreas.faerber@web.de> Cc: Alexander Graf <agraf@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-01-13 14:33:57 +01:00
L: qemu-ppc@nongnu.org
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
F: target-ppc/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/ppc/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S390
target-s390: Claim maintainership Signed-off-by: Richard Henderson <rth@twiddle.net>
2012-12-05 16:23:25 +01:00
M: Richard Henderson <rth@twiddle.net>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
M: Alexander Graf <agraf@suse.de>
S: Maintained
F: target-s390x/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/s390x/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
list of maintainers git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4393 c046a42c-6fe2-441c-8c8c-71466251a162
2008-05-09 11:39:00 +02:00
SH4
MAINTAINERS: Change MIPS and SH4 maintainers Since nobody else seems interested in maintaining MIPS and SH4 targets, and as I have done most of the recent code changes, let officialize that. Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2011-01-14 20:39:19 +01:00
M: Aurelien Jarno <aurelien@aurel32.net>
MAINTAINERS: Downgrade target-mips and target-sh4 to Odd Fixes Patches are not being handled, so let's downgrade to Odd Fixes. Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Aurélien Jarno <aurelien@aurel32.net>
2012-04-13 18:33:43 +02:00
S: Odd Fixes
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
F: target-sh4/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/sh4/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
SPARC
M: Blue Swirl <blauwirbel@gmail.com>
S: Maintained
F: target-sparc/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/sparc/
F: hw/sparc64/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: Add entry for UniCore32 Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Guan Xuetao <gxt@mprc.pku.edu.cn>
2012-03-14 00:45:43 +01:00
UniCore32
M: Guan Xuetao <gxt@mprc.pku.edu.cn>
S: Maintained
F: target-unicore32/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/unicore32/
MAINTAINERS: Add entry for UniCore32 Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Guan Xuetao <gxt@mprc.pku.edu.cn>
2012-03-14 00:45:43 +01:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
X86
M: qemu-devel@nongnu.org
S: Odd Fixes
F: target-i386/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/i386/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: add xtensa maintainer Add myself as target-xtensa and DC232B maintainer. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-09-06 01:55:56 +02:00
Xtensa
M: Max Filippov <jcmvbkbc@gmail.com>
MAINTAINERS: update wiki URL and machine names for target-xtensa Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-10-28 00:11:05 +02:00
W: http://wiki.osll.spb.ru/doku.php?id=etc:users:jcmvbkbc:qemu-target-xtensa
MAINTAINERS: add xtensa maintainer Add myself as target-xtensa and DC232B maintainer. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-09-06 01:55:56 +02:00
S: Maintained
F: target-xtensa/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/xtensa/
MAINTAINERS: add xtensa maintainer Add myself as target-xtensa and DC232B maintainer. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-09-06 01:55:56 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Guest CPU Cores (KVM):
----------------------
Overall
MAINTAINERS: Take over kvm maintenance Replace Avi with myself as kvm maintainer. Signed-off-by: Gleb Natapov <gleb@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-12-19 16:46:15 +01:00
M: Gleb Natapov <gleb@redhat.com>
MAINTAINERS: s/Marcelo/Paolo/ Marcelo doesn't maintain kvm anymore, Paolo is taking over the job. Update MAINTAINERS to stop flooding Marcelo with mail. Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2013-06-04 15:06:37 +02:00
M: Paolo Bonzini <pbonzini@redhat.com>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
L: kvm@vger.kernel.org
S: Supported
F: kvm-*
F: */kvm.*
MAINTAINERS: add entry for ARM KVM guest cores Add an entry indicating maintainer status for the ARM KVM code. Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2013-03-05 01:34:43 +01:00
ARM
M: Peter Maydell <peter.maydell@linaro.org>
S: Maintained
F: target-arm/kvm.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
PPC
M: Alexander Graf <agraf@suse.de>
S: Maintained
F: target-ppc/kvm.c
Add S390 maintainer information This patch adds information about who handles what when it comes to S390. I'll gladly support anything that's related to the device emulation model and S390 KVM parts. Since this patchset doesn't implement S390 CPU emulation, I left that part with a question mark. As soon as Uli's patchset gets committed I'd recommend setting him there. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2009-12-05 12:44:31 +01:00
S390
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
M: Alexander Graf <agraf@suse.de>
S: Maintained
F: target-s390x/kvm.c
X86
MAINTAINERS: Take over kvm maintenance Replace Avi with myself as kvm maintainer. Signed-off-by: Gleb Natapov <gleb@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-12-19 16:46:15 +01:00
M: Gleb Natapov <gleb@redhat.com>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
M: Marcelo Tosatti <mtosatti@redhat.com>
L: kvm@vger.kernel.org
S: Supported
F: target-i386/kvm.c
MAINTAINERS: add entry for Xen Acked-by: Alexander Graf <agraf@suse.de> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2011-07-29 17:05:13 +02:00
Guest CPU Cores (Xen):
----------------------
X86
M: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
L: xen-devel@lists.xensource.com
S: Supported
F: xen-*
F: */xen*
MAINTAINERS: Add a section for the host OS and a W32 maintainer Up to now, there was no special section for the different host operating systems used with QEMU. scripts/get_maintainer.pl did not show a maintainer for OS specific files and patches. Therefore I added three hosts systems: * POSIX for the majority of host systems which are supported. This includes BSD and Linux host systems. * LINUX is a special case of POSIX needed for some Linux specific files and directories. * W32, W64 for a well known family of closed source operating systems. I also added myself as a maintainer for W32, W64. Signed-off-by: Stefan Weil <sw@weilnetz.de> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-27 18:53:49 +01:00
Hosts:
------
LINUX
L: qemu-devel@nongnu.org
S: Maintained
F: linux-*
F: linux-headers/
POSIX
L: qemu-devel@nongnu.org
S: Maintained
F: *posix*
W32, W64
L: qemu-devel@nongnu.org
M: Stefan Weil <sw@weilnetz.de>
S: Maintained
F: *win32*
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
ARM Machines
------------
MAINTAINERS: Add maintainers for Exynos SOC. Signed-off-by: Evgeny Voevodin <e.voevodin@samsung.com> Acked-by: Andreas Färber <afaerber@suse.de> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2012-02-16 10:56:06 +01:00
Exynos
M: Evgeny Voevodin <e.voevodin@samsung.com>
M: Maksim Kozlov <m.kozlov@samsung.com>
MAINTAINERS: change Igor Mitsyanko's email address My email address in samsung.com domain is no longer accessible, change it to my personal gmail address. Signed-off-by: Igor Mitsyanko <i.mitsyanko@gmail.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-07-31 08:27:35 +02:00
M: Igor Mitsyanko <i.mitsyanko@gmail.com>
MAINTAINERS: Add maintainers for Exynos SOC. Signed-off-by: Evgeny Voevodin <e.voevodin@samsung.com> Acked-by: Andreas Färber <afaerber@suse.de> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2012-02-16 10:56:06 +01:00
M: Dmitry Solodkiy <d.solodkiy@samsung.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/exynos*
MAINTAINERS: Add maintainers for Exynos SOC. Signed-off-by: Evgeny Voevodin <e.voevodin@samsung.com> Acked-by: Andreas Färber <afaerber@suse.de> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2012-02-16 10:56:06 +01:00
MAINTAINERS: Add hw/highbank.c maintainer Signed-off-by: Mark Langsdorf <mark.langsdorf@calxeda.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2012-02-16 10:56:10 +01:00
Calxeda Highbank
M: Mark Langsdorf <mark.langsdorf@calxeda.com>
S: Supported
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/highbank.c
F: hw/net/xgmac.c
MAINTAINERS: Add hw/highbank.c maintainer Signed-off-by: Mark Langsdorf <mark.langsdorf@calxeda.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2012-02-16 10:56:10 +01:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Gumstix
M: qemu-devel@nongnu.org
S: Orphan
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/gumstix.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
i.MX31: KZM-ARM11-01 evaluation board Board support for Kyoto Micro's KZM-ARM11-01, an evaluation board built around the Freescale i.MX31. Signed-off-by: Philip O'Sullivan <philipo@ok-labs.com> Signed-off-by: Peter Chubb <peter.chubb@nicta.com.au> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2012-07-04 12:43:34 +02:00
i.MX31
M: Peter Chubb <peter.chubb@nicta.com.au>
S: Odd fixes
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/imx*
F: hw/arm/kzm.c
i.MX31: KZM-ARM11-01 evaluation board Board support for Kyoto Micro's KZM-ARM11-01, an evaluation board built around the Freescale i.MX31. Signed-off-by: Philip O'Sullivan <philipo@ok-labs.com> Signed-off-by: Peter Chubb <peter.chubb@nicta.com.au> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2012-07-04 12:43:34 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Integrator CP
M: Paul Brook <paul@codesourcery.com>
MAINTAINERS: update maintainer for target-arm and ARM devboards Add myself as co-maintainer alongside Paul Brook for the TCG ARM guest implementation (target-arm) and the ARM dev boards (integratorcp, realview, stellaris, versatilepb). Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Acked-by: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2011-09-20 17:18:46 +02:00
M: Peter Maydell <peter.maydell@linaro.org>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/integratorcp.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Mainstone
M: qemu-devel@nongnu.org
S: Orphan
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/mainstone.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Musicpal
M: Jan Kiszka <jan.kiszka@web.de>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/musicpal.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
nSeries
M: Andrzej Zaborowski <balrogg@gmail.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/nseries.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Palm
M: Andrzej Zaborowski <balrogg@gmail.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/palm.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Real View
M: Paul Brook <paul@codesourcery.com>
MAINTAINERS: update maintainer for target-arm and ARM devboards Add myself as co-maintainer alongside Paul Brook for the TCG ARM guest implementation (target-arm) and the ARM dev boards (integratorcp, realview, stellaris, versatilepb). Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Acked-by: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2011-09-20 17:18:46 +02:00
M: Peter Maydell <peter.maydell@linaro.org>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/realview*
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Spitz
M: Andrzej Zaborowski <balrogg@gmail.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/spitz.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Stellaris
M: Paul Brook <paul@codesourcery.com>
MAINTAINERS: update maintainer for target-arm and ARM devboards Add myself as co-maintainer alongside Paul Brook for the TCG ARM guest implementation (target-arm) and the ARM dev boards (integratorcp, realview, stellaris, versatilepb). Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Acked-by: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2011-09-20 17:18:46 +02:00
M: Peter Maydell <peter.maydell@linaro.org>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/stellaris*
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Versatile PB
M: Paul Brook <paul@codesourcery.com>
MAINTAINERS: update maintainer for target-arm and ARM devboards Add myself as co-maintainer alongside Paul Brook for the TCG ARM guest implementation (target-arm) and the ARM dev boards (integratorcp, realview, stellaris, versatilepb). Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Acked-by: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2011-09-20 17:18:46 +02:00
M: Peter Maydell <peter.maydell@linaro.org>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/versatile*
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
xilinx_zynq: machine model initial version Xilinx zynq-7000 machine model. Also includes device model for the zynq-specific system level control register (SLCR) module. Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2012-03-05 05:39:13 +01:00
Xilinx Zynq
M: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/arm/xilinx_zynq.c
F: hw/misc/zynq_slcr.c
F: hw/*/cadence_*
F: hw/ssi/xilinx_spips.c
xilinx_zynq: machine model initial version Xilinx zynq-7000 machine model. Also includes device model for the zynq-specific system level control register (SLCR) module. Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2012-03-05 05:39:13 +01:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
CRIS Machines
-------------
Axis Dev88
M: Edgar E. Iglesias <edgar.iglesias@gmail.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/cris/axis_dev88.c
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/*/etraxfs_*.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: add LatticeMico32 maintainer Add me as the lm32-target and machines maintainer. Signed-off-by: Michael Walle <michael@walle.cc> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2011-02-17 23:45:18 +01:00
LM32 Machines
-------------
EVR32 and uclinux BSP
M: Michael Walle <michael@walle.cc>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/lm32/lm32_boards.c
MAINTAINERS: add LatticeMico32 maintainer Add me as the lm32-target and machines maintainer. Signed-off-by: Michael Walle <michael@walle.cc> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2011-02-17 23:45:18 +01:00
MAINTAINERS: add Milkymist board Signed-off-by: Michael Walle <michael@walle.cc> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2011-03-07 23:32:45 +01:00
milkymist
M: Michael Walle <michael@walle.cc>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/lm32/milkymist.c
MAINTAINERS: add Milkymist board Signed-off-by: Michael Walle <michael@walle.cc> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2011-03-07 23:32:45 +01:00
MAINTAINERS: fix typos Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2011-01-14 20:39:19 +01:00
M68K Machines
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
-------------
an5206
M: Paul Brook <paul@codesourcery.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/m68k/an5206.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
dummy_m68k
M: Paul Brook <paul@codesourcery.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/m68k/dummy_m68k.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
mcf5208
M: Paul Brook <paul@codesourcery.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/m68k/mcf5208.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MicroBlaze Machines
-------------------
petalogix_s3adsp1800
M: Edgar E. Iglesias <edgar.iglesias@gmail.com>
S: Maintained
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/microblaze/petalogix_s3adsp1800_mmu.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: Add Petalogix ml605 machine model Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2012-06-26 06:29:40 +02:00
petalogix_ml605
M: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/microblaze/petalogix_ml605_mmu.c
MAINTAINERS: Add Petalogix ml605 machine model Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2012-06-26 06:29:40 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MIPS Machines
-------------
Jazz
M: Hervé Poussineau <hpoussin@reactos.org>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/mips/mips_jazz.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Malta
M: Aurelien Jarno <aurelien@aurel32.net>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/mips/mips_malta.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Mipssim
M: qemu-devel@nongnu.org
S: Orphan
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/mips/mips_mipssim.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
R4000
M: Aurelien Jarno <aurelien@aurel32.net>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/mips/mips_r4k.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: Add myself into MAINTAINERS file Add myself into MAINTAINERS file, I'll looking at target-openrisc and hw/openrisc. Signed-off-by: Jia Liu <proljc@gmail.com> Message-id: 1372769717-852-1-git-send-email-proljc@gmail.com Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-07-02 14:55:17 +02:00
OpenRISC Machines
-----------------
or1k-sim
M: Jia Liu <proljc@gmail.com>
S: Maintained
F: hw/openrisc/openrisc_sim.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
PowerPC Machines
----------------
405
M: Alexander Graf <agraf@suse.de>
MAINTAINERS: Add qemu-ppc to all ppc target stuff Signed-off-by: Andreas Färber <andreas.faerber@web.de> Cc: Alexander Graf <agraf@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-01-13 14:33:57 +01:00
L: qemu-ppc@nongnu.org
MAINTAINERS: Downgrade ppc405 to Odd Fixes As requested by Alex. Signed-off-by: Andreas Färber <afaerber@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:46 +02:00
S: Odd Fixes
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/ppc/ppc405_boards.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: Document Bamboo machine and ppc4xx devices Place it in alphabetical order and add new Devices section ppc4xx to share file rules with 405 and virtex_ml507. Signed-off-by: Andreas Färber <afaerber@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:47 +02:00
Bamboo
M: Alexander Graf <agraf@suse.de>
L: qemu-ppc@nongnu.org
S: Odd Fixes
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/ppc/ppc440_bamboo.c
MAINTAINERS: Document Bamboo machine and ppc4xx devices Place it in alphabetical order and add new Devices section ppc4xx to share file rules with 405 and virtex_ml507. Signed-off-by: Andreas Färber <afaerber@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:47 +02:00
MAINTAINERS: Document e500 machines and devices Signed-off-by: Andreas Färber <afaerber@suse.de> Cc: Alexander Graf <agraf@suse.de> Cc: Scott Wood <scottwood@freescale.com> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:45 +02:00
e500
M: Alexander Graf <agraf@suse.de>
M: Scott Wood <scottwood@freescale.com>
L: qemu-ppc@nongnu.org
S: Supported
F: hw/ppc/e500.[hc]
F: hw/ppc/e500plat.c
mpc8544ds
M: Alexander Graf <agraf@suse.de>
M: Scott Wood <scottwood@freescale.com>
L: qemu-ppc@nongnu.org
S: Supported
F: hw/ppc/mpc8544ds.c
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/ppc/mpc8544_guts.c
MAINTAINERS: Document e500 machines and devices Signed-off-by: Andreas Färber <afaerber@suse.de> Cc: Alexander Graf <agraf@suse.de> Cc: Scott Wood <scottwood@freescale.com> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:45 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
New World
M: Alexander Graf <agraf@suse.de>
MAINTAINERS: Add qemu-ppc to all ppc target stuff Signed-off-by: Andreas Färber <andreas.faerber@web.de> Cc: Alexander Graf <agraf@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-01-13 14:33:57 +01:00
L: qemu-ppc@nongnu.org
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
ppc: Move Mac machines to hw/ppc/ Signed-off-by: Andreas Färber <afaerber@suse.de> [agraf: squash in MAINTAINERS fix] Signed-off-by: Alexander Graf <agraf@suse.de>
2013-01-24 00:03:54 +01:00
F: hw/ppc/mac_newworld.c
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/pci-host/uninorth.c
F: hw/pci-bridge/dec.[hc]
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/misc/macio/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Old World
M: Alexander Graf <agraf@suse.de>
MAINTAINERS: Add qemu-ppc to all ppc target stuff Signed-off-by: Andreas Färber <andreas.faerber@web.de> Cc: Alexander Graf <agraf@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-01-13 14:33:57 +01:00
L: qemu-ppc@nongnu.org
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
ppc: Move Mac machines to hw/ppc/ Signed-off-by: Andreas Färber <afaerber@suse.de> [agraf: squash in MAINTAINERS fix] Signed-off-by: Alexander Graf <agraf@suse.de>
2013-01-24 00:03:54 +01:00
F: hw/ppc/mac_oldworld.c
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/pci-host/grackle.c
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/misc/macio/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: Add PReP maintainer Officially take on maintainership for PReP and upgrade to Odd Fixes. Acked-by: Alexander Graf <agraf@suse.de> Signed-off-by: Andreas Färber <andreas.faerber@web.de> Cc: Alexander Graf <agraf@suse.de> Cc: Hervé Poussineau <hpoussin@reactos.org> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2011-11-01 00:03:07 +01:00
PReP
M: Andreas Färber <andreas.faerber@web.de>
MAINTAINERS: Add qemu-ppc to all ppc target stuff Signed-off-by: Andreas Färber <andreas.faerber@web.de> Cc: Alexander Graf <agraf@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-01-13 14:33:57 +01:00
L: qemu-ppc@nongnu.org
MAINTAINERS: Add PReP maintainer Officially take on maintainership for PReP and upgrade to Odd Fixes. Acked-by: Alexander Graf <agraf@suse.de> Signed-off-by: Andreas Färber <andreas.faerber@web.de> Cc: Alexander Graf <agraf@suse.de> Cc: Hervé Poussineau <hpoussin@reactos.org> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2011-11-01 00:03:07 +01:00
S: Odd Fixes
prep: Move PReP machine to hw/ppc/ Signed-off-by: Andreas Färber <andreas.faerber@web.de>
2013-01-26 20:41:58 +01:00
F: hw/ppc/prep.c
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/pci-host/prep.[hc]
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/isa/pc87312.[hc]
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: Document sPAPR (pSeries) machine Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:44 +02:00
sPAPR
M: Alexander Graf <agraf@suse.de>
L: qemu-ppc@nongnu.org
S: Supported
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/spapr*
pseries: Update MAINTAINERS information I'm no longer at IBM, and therefore no long actively working on the pseries (aka sPAPR) qemu machine type. This patch removes my information in the MAINTAINERS file. While we're at it, I've added some extra file patterns for pseries specific files that weren't included in the existing pattern. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> [agraf: Remove new maintainer addition] Signed-off-by: Alexander Graf <agraf@suse.de>
2013-06-15 03:51:52 +02:00
F: include/hw/*/spapr*
F: hw/*/xics*
F: include/hw/*/xics*
F: pc-bios/spapr-rtas/*
MAINTAINERS: Document sPAPR (pSeries) machine Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:44 +02:00
MAINTAINERS: Document virtex_ml507 machine Place it in alphabetical order, there is a separate section for sharing ppc4xx devices now. Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:48 +02:00
virtex_ml507
M: Edgar E. Iglesias <edgar.iglesias@gmail.com>
L: qemu-ppc@nongnu.org
S: Odd Fixes
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/ppc/virtex_ml507.c
MAINTAINERS: Document virtex_ml507 machine Place it in alphabetical order, there is a separate section for sharing ppc4xx devices now. Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:48 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
SH4 Machines
------------
R2D
M: Magnus Damm <magnus.damm@gmail.com>
S: Maintained
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/sh4/r2d.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Shix
M: Magnus Damm <magnus.damm@gmail.com>
MAINTAINERS: fix typos Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2011-01-14 20:39:19 +01:00
S: Orphan
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/sh4/shix.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
SPARC Machines
--------------
Sun4m
M: Blue Swirl <blauwirbel@gmail.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/sparc/sun4m.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Sun4u
M: Blue Swirl <blauwirbel@gmail.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/sparc64/sun4u.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Add MAINTAINERS entry for leon3 Signed-off-by: Fabien Chouteau <chouteau@adacore.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2012-05-22 10:14:28 +02:00
Leon3
M: Fabien Chouteau <chouteau@adacore.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/sparc/leon3.c
F: hw/*/grlib*
Add MAINTAINERS entry for leon3 Signed-off-by: Fabien Chouteau <chouteau@adacore.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2012-05-22 10:14:28 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S390 Machines
-------------
S390 Virtio
M: Alexander Graf <agraf@suse.de>
S: Maintained
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/s390x/s390-*.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
s390: virtio-ccw maintainer Add myself as maintainer for virtio-ccw and the s390-ccw-virtio machine. Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com> [agraf: add myself for virtio-ccw machine] Signed-off-by: Alexander Graf <agraf@suse.de>
2013-03-05 03:22:01 +01:00
S390 Virtio-ccw
M: Cornelia Huck <cornelia.huck@de.ibm.com>
M: Alexander Graf <agraf@suse.de>
S: Supported
F: hw/s390x/s390-virtio-ccw.c
F: hw/s390x/css.[hc]
T: git git://github.com/cohuck/qemu virtio-ccw-upstr
unicore32-softmmu: Add maintainer information for UniCore32 machine Signed-off-by: Guan Xuetao <gxt@mprc.pku.edu.cn> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2012-08-10 08:42:34 +02:00
UniCore32 Machines
-------------
PKUnity-3 SoC initramfs-with-busybox
M: Guan Xuetao <gxt@mprc.pku.edu.cn>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/puv3*
unicore32-softmmu: Add maintainer information for UniCore32 machine Signed-off-by: Guan Xuetao <gxt@mprc.pku.edu.cn> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2012-08-10 08:42:34 +02:00
F: hw/unicore32/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
X86 Machines
------------
PC
Change email address My IBM email address will be unaccessible after August 23rd, 2013. Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
2013-08-19 15:49:37 +02:00
M: Anthony Liguori <anthony@codemonkey.ws>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Supported
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/i386/pc.[ch]
F: hw/i386/pc_piix.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: add xtensa maintainer Add myself as target-xtensa and DC232B maintainer. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-09-06 01:55:56 +02:00
Xtensa Machines
---------------
MAINTAINERS: update wiki URL and machine names for target-xtensa Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-10-28 00:11:05 +02:00
sim
MAINTAINERS: add xtensa maintainer Add myself as target-xtensa and DC232B maintainer. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-09-06 01:55:56 +02:00
M: Max Filippov <jcmvbkbc@gmail.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/xtensa/xtensa_sim.c
MAINTAINERS: update wiki URL and machine names for target-xtensa Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-10-28 00:11:05 +02:00
Avnet LX60
M: Max Filippov <jcmvbkbc@gmail.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/xtensa/xtensa_lx60.c
MAINTAINERS: add xtensa maintainer Add myself as target-xtensa and DC232B maintainer. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-09-06 01:55:56 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Devices
-------
IDE
M: Kevin Wolf <kwolf@redhat.com>
S: Odd Fixes
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: include/hw/ide.h
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
F: hw/ide/
MAINTAINERS: claim maintainership for the OMAP devices Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2011-09-17 18:26:15 +02:00
OMAP
M: Peter Maydell <peter.maydell@linaro.org>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/omap*
MAINTAINERS: claim maintainership for the OMAP devices Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2011-09-17 18:26:15 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
PCI
M: Michael S. Tsirkin <mst@redhat.com>
S: Supported
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: include/hw/pci/*
MAINTAINERS: add hw/pci/ to list of PCI files Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2012-12-12 14:11:55 +01:00
F: hw/pci/*
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/acpi/*
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: Document Bamboo machine and ppc4xx devices Place it in alphabetical order and add new Devices section ppc4xx to share file rules with 405 and virtex_ml507. Signed-off-by: Andreas Färber <afaerber@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:47 +02:00
ppc4xx
M: Alexander Graf <agraf@suse.de>
L: qemu-ppc@nongnu.org
S: Odd Fixes
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/ppc/ppc4*.c
MAINTAINERS: Document Bamboo machine and ppc4xx devices Place it in alphabetical order and add new Devices section ppc4xx to share file rules with 405 and virtex_ml507. Signed-off-by: Andreas Färber <afaerber@suse.de> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:47 +02:00
MAINTAINERS: Document e500 machines and devices Signed-off-by: Andreas Färber <afaerber@suse.de> Cc: Alexander Graf <agraf@suse.de> Cc: Scott Wood <scottwood@freescale.com> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:45 +02:00
ppce500
M: Alexander Graf <agraf@suse.de>
M: Scott Wood <scottwood@freescale.com>
L: qemu-ppc@nongnu.org
S: Supported
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/ppc/e500*
MAINTAINERS: Document e500 machines and devices Signed-off-by: Andreas Färber <afaerber@suse.de> Cc: Alexander Graf <agraf@suse.de> Cc: Scott Wood <scottwood@freescale.com> Signed-off-by: Alexander Graf <agraf@suse.de>
2012-08-22 07:48:45 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
SCSI
split SCSI and LSI, add myself as SCSI maintainer This has been the de facto situation for a while now. Add a tree, too. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-02-22 15:59:52 +01:00
M: Paolo Bonzini <pbonzini@redhat.com>
S: Supported
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: include/hw/scsi*
F: hw/scsi/*
MAINTAINERS: Indicate type of SCM T: lines are supposed to indicate whether it's git. Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-04-13 18:03:42 +02:00
T: git git://github.com/bonzini/qemu.git scsi-next
split SCSI and LSI, add myself as SCSI maintainer This has been the de facto situation for a while now. Add a tree, too. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-02-22 15:59:52 +01:00
LSI53C895A
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
M: Paul Brook <paul@codesourcery.com>
S: Odd Fixes
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/scsi/lsi53c895a.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: Added maintainerships for SSI Added maintainership for SSI, M25P80 and the Xilinx SPI controllers. Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Acked-by: Peter Maydell <peter.maydell@linaro.org>
2012-08-06 03:38:19 +02:00
SSI
M: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/ssi/*
F: hw/block/m25p80.c
MAINTAINERS: Added maintainerships for SSI Added maintainership for SSI, M25P80 and the Xilinx SPI controllers. Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Acked-by: Peter Maydell <peter.maydell@linaro.org>
2012-08-06 03:38:19 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
USB
usb: update MAINTAINERS Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
2010-12-17 11:11:25 +01:00
M: Gerd Hoffmann <kraxel@redhat.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/usb/*
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
vfio: Enable vfio-pci and mark supported Enabled for all softmmu guests supporting PCI on Linux hosts. Note that currently only x86 hosts have the kernel side VFIO IOMMU support for this. PPC (g3beige) is the only non-x86 guest known to work. ARM (veratile) hangs in firmware, others untested. Signed-off-by: Alex Williamson <alex.williamson@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-09-26 19:19:39 +02:00
VFIO
M: Alex Williamson <alex.williamson@redhat.com>
S: Supported
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: hw/misc/vfio.c
vfio: Enable vfio-pci and mark supported Enabled for all softmmu guests supporting PCI on Linux hosts. Note that currently only x86 hosts have the kernel side VFIO IOMMU support for this. PPC (g3beige) is the only non-x86 guest known to work. ARM (veratile) hangs in firmware, others untested. Signed-off-by: Alex Williamson <alex.williamson@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-09-26 19:19:39 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
vhost
M: Michael S. Tsirkin <mst@redhat.com>
S: Supported
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/*vhost*
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
virtio
Change email address My IBM email address will be unaccessible after August 23rd, 2013. Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
2013-08-19 15:49:37 +02:00
M: Anthony Liguori <anthony@codemonkey.ws>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Supported
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/virtio*
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
virtio-9p
hw/9pfs: Update MAINTAINERS file Acked-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-19 18:27:11 +01:00
M: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Supported
MAINTAINERS: Fix virtio-9p file pattern Only one pattern is allowed per F: line, split in two. Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
2012-04-13 17:19:12 +02:00
F: hw/9pfs/
F: fsdev/
MAINTAINERS: Fix SCM tree for virtio-9p Instead of a Web link, T: is supposed to indicate type of SCM and pullable URL, so switch to the git:// URL. Also harmonize the spacing between sections while at it. Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
2012-04-13 18:23:55 +02:00
T: git git://github.com/kvaneesh/QEMU.git
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
virtio-blk
M: Kevin Wolf <kwolf@redhat.com>
MAINTAINERS: add Stefan Hajnoczi as block and virtio-blk co-maintainer Kevin has requested co-maintainership to give him more time to write code. We will alternate patch review duties on a weekly basis. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
2012-11-09 14:29:03 +01:00
M: Stefan Hajnoczi <stefanha@redhat.com>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Supported
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/block/virtio-blk.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
s390: virtio-ccw maintainer Add myself as maintainer for virtio-ccw and the s390-ccw-virtio machine. Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com> [agraf: add myself for virtio-ccw machine] Signed-off-by: Alexander Graf <agraf@suse.de>
2013-03-05 03:22:01 +01:00
virtio-ccw
M: Cornelia Huck <cornelia.huck@de.ibm.com>
S: Supported
F: hw/s390x/virtio-ccw.[hc]
T: git git://github.com/cohuck/qemu virtio-ccw-upstr
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
virtio-serial
M: Amit Shah <amit.shah@redhat.com>
S: Supported
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/char/virtio-serial-bus.c
F: hw/char/virtio-console.c
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
NVMe: Initial commit for new storage interface Initial commit for emulated Non-Volatile-Memory Express (NVMe) pci storage device. NVMe is an open, industry driven storage specification defining an optimized register and command set designed to deliver the full capabilities of non-volatile memory on PCIe SSDs. Further information may be found on the organizations website at: http://www.nvmexpress.org/ This commit implements the minimum from the specification to work with existing drivers. Cc: Keith Busch <keith.busch@gmail.com> Signed-off-by: Keith Busch <keith.busch@intel.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
2013-06-04 17:17:10 +02:00
nvme
M: Keith Busch <keith.busch@intel.com>
S: Supported
F: hw/block/nvme*
MAINTAINERS: Added Xilinx EDK devices Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2012-06-26 06:29:41 +02:00
Xilinx EDK
M: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
M: Edgar E. Iglesias <edgar.iglesias@gmail.com>
S: Maintained
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/*/xilinx_*
F: include/hw/xilinx.h
MAINTAINERS: Added Xilinx EDK devices Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2012-06-26 06:29:41 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Subsystems
----------
Audio
M: Vassili Karpov (malc) <av1474@comtv.ru>
S: Maintained
F: audio/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/audio/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Block
M: Kevin Wolf <kwolf@redhat.com>
MAINTAINERS: add Stefan Hajnoczi as block and virtio-blk co-maintainer Kevin has requested co-maintainership to give him more time to write code. We will alternate patch review duties on a weekly basis. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
2012-11-09 14:29:03 +01:00
M: Stefan Hajnoczi <stefanha@redhat.com>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Supported
F: block*
F: block/
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/block/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Character Devices
Change email address My IBM email address will be unaccessible after August 23rd, 2013. Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
2013-08-19 15:49:37 +02:00
M: Anthony Liguori <anthony@codemonkey.ws>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
F: qemu-char.c
MAINTAINERS: Add entry for QOM CPU Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-09-17 19:10:32 +02:00
CPU
M: Andreas Färber <afaerber@suse.de>
S: Supported
F: qom/cpu.c
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: include/qom/cpu.h
MAINTAINERS: Include X86CPU in CPU maintenance area Document that the x86 CPU refactorings are going through the qom-cpu tree. This does not contradict the established practice that patches adding KVM features to the x86 CPU go through the KVM maintainers, it merely takes it out of target-i386 TCG's Odd Fixes status. Signed-off-by: Andreas Färber <afaerber@suse.de> Cc: Marcello Tosatti <mtosatti@redhat.com>
2012-12-09 20:15:31 +01:00
F: target-i386/cpu.c
MAINTAINERS: Add entry for QOM CPU Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-09-17 19:10:32 +02:00
target-i386: Introduce ICC bus/device/bridge Provides a hotpluggable bus for APIC and CPU. * icc-bridge will serve as a parent for icc-bus and provide mmio mapping services to child icc-devices. * icc-device will replace SysBusDevice as a parent of APIC and IOAPIC devices. Signed-off-by: Igor Mammedov <imammedo@redhat.com> Signed-off-by: Andreas Färber <afaerber@suse.de>
2013-04-29 17:02:50 +02:00
ICC Bus
M: Igor Mammedov <imammedo@redhat.com>
S: Supported
F: include/hw/cpu/icc_bus.h
F: hw/cpu/icc_bus.c
MAINTAINERS: Added device tree Agreed between myself and Alex: http://lists.nongnu.org/archive/html/qemu-devel/2012-06/msg03561.html Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Acked-by: Alexander Graf <agraf@suse.de> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2012-06-26 06:29:42 +02:00
Device Tree
M: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
M: Alexander Graf <agraf@suse.de>
S: Maintained
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: device_tree.[ch]
MAINTAINERS: Added device tree Agreed between myself and Alex: http://lists.nongnu.org/archive/html/qemu-devel/2012-06/msg03561.html Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com> Acked-by: Alexander Graf <agraf@suse.de> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
2012-06-26 06:29:42 +02:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
GDB stub
M: qemu-devel@nongnu.org
S: Odd Fixes
F: gdbstub*
F: gdb-xml/
spice: MAINTAINERS update
2010-12-13 21:30:37 +01:00
SPICE
M: Gerd Hoffmann <kraxel@redhat.com>
S: Supported
MAINTAINERS: fix bad F: patterns This patch fixes a number of incorrect F: patterns which didn't match any files in the source tree. This was caused by a mix of minor typos (- for _ and the like) and a few entries which hadn't been correctly updated following the rearrangement of hw/. Offending entries were located with the following shell rune: for pattern in $(sed -ne 's/^F: //p' MAINTAINERS); do if ! stat --printf='' $pattern 2>/dev/null; then echo bad pattern: $pattern fi done Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com> Message-id: 1372070972-30776-1-git-send-email-peter.maydell@linaro.org Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 12:49:32 +02:00
F: include/ui/qemu-spice.h
spice: MAINTAINERS update
2010-12-13 21:30:37 +01:00
F: ui/spice-*.c
F: audio/spiceaudio.c
MAINTAINERS: update for source code movement Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2013-02-04 15:19:30 +01:00
F: hw/display/qxl*
spice: MAINTAINERS update
2010-12-13 21:30:37 +01:00
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Graphics
Change email address My IBM email address will be unaccessible after August 23rd, 2013. Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
2013-08-19 15:49:37 +02:00
M: Anthony Liguori <anthony@codemonkey.ws>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
F: ui/
MAINTAINERS: Add Cocoa maintainer Degrade cocoa.m from Maintained to Odd Fixes. Signed-off-by: Andreas Färber <andreas.faerber@web.de> Cc: Anthony Liguori <aliguori@us.ibm.com>
2011-10-30 18:08:01 +01:00
Cocoa graphics
M: Andreas Färber <andreas.faerber@web.de>
S: Odd Fixes
F: ui/cocoa.m
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Main loop
Change email address My IBM email address will be unaccessible after August 23rd, 2013. Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
2013-08-19 15:49:37 +02:00
M: Anthony Liguori <anthony@codemonkey.ws>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Supported
F: vl.c
MAINTAINERS: split Monitor (QMP/HMP) entry This entry doesn't reflect reality for a few years now. This commit splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped as a maintainer. This is what we have been for the last few years. Also, it's going to help me to offload some of this work to someone else in the near future. Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> Acked-by: Markus Armbruster <armbru@redhat.com>
2013-06-03 17:14:26 +02:00
Human Monitor (HMP)
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
M: Luiz Capitulino <lcapitulino@redhat.com>
S: Supported
F: monitor.c
MAINTAINERS: split Monitor (QMP/HMP) entry This entry doesn't reflect reality for a few years now. This commit splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped as a maintainer. This is what we have been for the last few years. Also, it's going to help me to offload some of this work to someone else in the near future. Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> Acked-by: Markus Armbruster <armbru@redhat.com>
2013-06-03 17:14:26 +02:00
F: hmp.c
F: hmp-commands.hx
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Network device layer
Change email address My IBM email address will be unaccessible after August 23rd, 2013. Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
2013-08-19 15:49:37 +02:00
M: Anthony Liguori <anthony@codemonkey.ws>
MAINTAINERS: Update email address for Stefan Hajnoczi Switch to my new work email address from which I am contributing. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2012-10-07 18:08:49 +02:00
M: Stefan Hajnoczi <stefanha@redhat.com>
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
S: Maintained
F: net/
MAINTAINERS: Replace net maintainer Mark McLoughlin with Stefan Hajnoczi The net subsystem has lacked an active maintainer since 2009. I have built and tested a net-next tree to get the ball rolling again. Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
2012-07-20 15:29:24 +02:00
T: git git://github.com/stefanha/qemu.git net
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
nbd: add myself as maintainer Not planning to do much else, hence listing it as "Odd Fixes". Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2011-12-22 11:39:19 +01:00
Network Block Device (NBD)
M: Paolo Bonzini <pbonzini@redhat.com>
S: Odd Fixes
F: block/nbd.c
F: nbd.*
F: qemu-nbd.c
MAINTAINERS: Indicate type of SCM T: lines are supposed to indicate whether it's git. Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-04-13 18:03:42 +02:00
T: git git://github.com/bonzini/qemu.git nbd-next
nbd: add myself as maintainer Not planning to do much else, hence listing it as "Odd Fixes". Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2011-12-22 11:39:19 +01:00
MAINTAINERS: split Monitor (QMP/HMP) entry This entry doesn't reflect reality for a few years now. This commit splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped as a maintainer. This is what we have been for the last few years. Also, it's going to help me to offload some of this work to someone else in the near future. Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> Acked-by: Markus Armbruster <armbru@redhat.com>
2013-06-03 17:14:26 +02:00
QAPI
M: Luiz Capitulino <lcapitulino@redhat.com>
M: Michael Roth <mdroth@linux.vnet.ibm.com>
S: Supported
F: qapi/
MAINTAINERS: new maintainers for qapi-schema.json I'm facing two problems lately wrt QMP patch review: increasingly lack of bandwidth and lack of background in so many different areas that are getting new QMP commands almost every week. In order to help me mitigate this problem, I'm adding Eric and Markus (besides me) as maintainers of the qapi-schema.json file. Markus has been an old timer reviewer. Eric is being the most active and prolific reviewer of QMP patches for some time now. I believe Markus and Eric will keep doing their work as before, but starting now I'll require the ACK of at least one of them before appling a patch/series that touches the qapi-schema.json file. Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Acked-by: Markus Armbruster <armbru@redhat.com>
2013-06-03 17:11:53 +02:00
QAPI Schema
M: Eric Blake <eblake@redhat.com>
M: Luiz Capitulino <lcapitulino@redhat.com>
M: Markus Armbruster <armbru@redhat.com>
S: Supported
F: qapi-schema.json
MAINTAINERS: split Monitor (QMP/HMP) entry This entry doesn't reflect reality for a few years now. This commit splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped as a maintainer. This is what we have been for the last few years. Also, it's going to help me to offload some of this work to someone else in the near future. Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> Acked-by: Markus Armbruster <armbru@redhat.com>
2013-06-03 17:14:26 +02:00
QMP
M: Luiz Capitulino <lcapitulino@redhat.com>
S: Supported
F: qmp.c
F: monitor.c
F: qmp-commands.hx
F: QMP/
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
SLIRP
slirp: Take maintainer token Anthony asked me to pick up the maintenance of this subsystem, and I agreed. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2011-07-27 14:21:32 +02:00
M: Jan Kiszka <jan.kiszka@siemens.com>
S: Maintained
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
F: slirp/
MAINTAINERS: Indicate type of SCM T: lines are supposed to indicate whether it's git. Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-04-13 18:03:42 +02:00
T: git git://git.kiszka.org/qemu.git queues/slirp
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
MAINTAINERS: add tracing subsystem Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
2011-09-03 17:24:47 +02:00
Tracing
MAINTAINERS: Update email address for Stefan Hajnoczi Switch to my new work email address from which I am contributing. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2012-10-07 18:08:49 +02:00
M: Stefan Hajnoczi <stefanha@redhat.com>
MAINTAINERS: add tracing subsystem Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
2011-09-03 17:24:47 +02:00
S: Maintained
F: trace/
tracetool: Add MAINTAINERS info Update the MAINTAINERS file to reflect the new Python tracetool code. [Commit description written by Stefan Hajnoczi] Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
2012-04-03 20:48:17 +02:00
F: scripts/tracetool.py
F: scripts/tracetool/
maintainers: Add docs/tracing.txt to Tracing The topic of whether and by whom docs/tracing.txt is maintained was brought up. It currently does not have an official maintainer. Add it to the tracing section so that Stefan gets cc'ed on patches. Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> Cc: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
2012-03-10 13:37:34 +01:00
F: docs/tracing.txt
MAINTAINERS: Indicate type of SCM T: lines are supposed to indicate whether it's git. Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-04-13 18:03:42 +02:00
T: git git://github.com/stefanha/qemu.git tracing
MAINTAINERS: add tracing subsystem Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
2011-09-03 17:24:47 +02:00
MAINTAINERS: add checkpatch Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-11-26 10:51:23 +01:00
Checkpatch
M: Blue Swirl <blauwirbel@gmail.com>
S: Odd Fixes
F: scripts/checkpatch.pl
Use a Linux-style MAINTAINERS file I make no claims that this is accurate or exhaustive but I think it's a reasonable place to start. As the file mentions, the purpose of this file is to give contributors information about who they can go to with questions about a particular piece of code or who they can ask for review. If you sign up for a piece of code and indicate that it's Maintained or Supported, please be prepared to be responsive to questions about that subsystem. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- v1 -> v2 - Sort alphabetically - Copy in instructions from linux MAINTAINERS - Fix entries based on review feedback
2010-09-09 21:51:31 +02:00
Usermode Emulation
------------------
BSD user
M: Blue Swirl <blauwirbel@gmail.com>
S: Maintained
F: bsd-user/
Linux user
M: Riku Voipio <riku.voipio@iki.fi>
S: Maintained
F: linux-user/
MAINTAINERS: add entries for TCG The MAINTAINERS file was lacking entries concerning the TCG code, add them based on the git history. For the common TCG code, is probably better to keep qemu-devel@non-gnu.org as this code can break easily, so it's better to get it reviewed by a few persons. Acked-by: Alexander Graf <agraf@suse.de> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2011-01-14 20:39:19 +01:00
Tiny Code Generator (TCG)
-------------------------
Common code
M: qemu-devel@nongnu.org
tcg: Add myself to general TCG maintainership Acked-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Richard Henderson <rth@twiddle.net>
2013-07-03 20:09:03 +02:00
M: Richard Henderson <rth@twiddle.net>
MAINTAINERS: add entries for TCG The MAINTAINERS file was lacking entries concerning the TCG code, add them based on the git history. For the common TCG code, is probably better to keep qemu-devel@non-gnu.org as this code can break easily, so it's better to get it reviewed by a few persons. Acked-by: Alexander Graf <agraf@suse.de> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2011-01-14 20:39:19 +01:00
S: Maintained
F: tcg/
MAINTAINERS: add tcg/aarch64 maintainer Signed-off-by: Claudio Fontana <claudio.fontana@huawei.com> Message-id: 51ACA0B2.80800@huawei.com Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2013-06-12 17:20:24 +02:00
AArch64 target
M: Claudio Fontana <claudio.fontana@huawei.com>
M: Claudio Fontana <claudio.fontana@gmail.com>
S: Maintained
F: tcg/aarch64/
MAINTAINERS: add entries for TCG The MAINTAINERS file was lacking entries concerning the TCG code, add them based on the git history. For the common TCG code, is probably better to keep qemu-devel@non-gnu.org as this code can break easily, so it's better to get it reviewed by a few persons. Acked-by: Alexander Graf <agraf@suse.de> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2011-01-14 20:39:19 +01:00
ARM target
M: Andrzej Zaborowski <balrogg@gmail.com>
S: Maintained
F: tcg/arm/
HPPA target
M: Richard Henderson <rth@twiddle.net>
S: Maintained
F: tcg/hppa/
i386 target
M: qemu-devel@nongnu.org
S: Maintained
F: tcg/i386/
IA64 target
M: Aurelien Jarno <aurelien@aurel32.net>
S: Maintained
F: tcg/ia64/
MIPS target
MAINTAINERS: Fix typo in email address Fix a typo in one of the copies of Aurelien Jarno's email address. Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
2011-06-22 16:45:01 +02:00
M: Aurelien Jarno <aurelien@aurel32.net>
MAINTAINERS: add entries for TCG The MAINTAINERS file was lacking entries concerning the TCG code, add them based on the git history. For the common TCG code, is probably better to keep qemu-devel@non-gnu.org as this code can break easily, so it's better to get it reviewed by a few persons. Acked-by: Alexander Graf <agraf@suse.de> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2011-01-14 20:39:19 +01:00
S: Maintained
F: tcg/mips/
PPC
M: Vassili Karpov (malc) <av1474@comtv.ru>
S: Maintained
F: tcg/ppc/
PPC64 target
M: Vassili Karpov (malc) <av1474@comtv.ru>
S: Maintained
F: tcg/ppc64/
S390 target
M: Alexander Graf <agraf@suse.de>
M: Richard Henderson <rth@twiddle.net>
S: Maintained
F: tcg/s390/
SPARC target
M: Blue Swirl <blauwirbel@gmail.com>
S: Maintained
F: tcg/sparc/
tci: Add entry to MAINTAINERS This should have be part of my TCI patch series. Signed-off-by: Stefan Weil <sw@weilnetz.de> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2011-11-24 23:20:43 +01:00
TCI target
M: Stefan Weil <sw@weilnetz.de>
S: Maintained
MAINTAINERS: Fix TCI file pattern tcg/tci is a directory, so for recursive semantics add a trailing slash. Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Stefan Weil <sw@weilnetz.de>
2012-04-13 17:22:03 +02:00
F: tcg/tci/
MAINTAINERS: Document all stable trees We currently host stable trees for 0.10, 0.14, 0.15 and 1.0. Sort in descending order. It is expected that further non-stable sections will be added above these so this order avoids scrolling through an ever-growing list of stable trees. Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-04-13 17:52:27 +02:00
Stable branches
---------------
Stable 1.0
L: qemu-stable@nongnu.org
T: git git://git.qemu.org/qemu-stable-1.0.git
S: Orphan
Stable 0.15
L: qemu-stable@nongnu.org
MAINTAINERS: Take over 0.15 maintenance SUSE is shipping qemu-kvm 0.15.1 with SLES 11 SP2 so we will be actively tracking all KVM-related issues. Therefore upgrade to Supported. Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-04-13 17:54:02 +02:00
M: Andreas Färber <afaerber@suse.de>
MAINTAINERS: Document all stable trees We currently host stable trees for 0.10, 0.14, 0.15 and 1.0. Sort in descending order. It is expected that further non-stable sections will be added above these so this order avoids scrolling through an ever-growing list of stable trees. Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-04-13 17:52:27 +02:00
T: git git://git.qemu.org/qemu-stable-0.15.git
MAINTAINERS: Take over 0.15 maintenance SUSE is shipping qemu-kvm 0.15.1 with SLES 11 SP2 so we will be actively tracking all KVM-related issues. Therefore upgrade to Supported. Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-04-13 17:54:02 +02:00
S: Supported
MAINTAINERS: Document all stable trees We currently host stable trees for 0.10, 0.14, 0.15 and 1.0. Sort in descending order. It is expected that further non-stable sections will be added above these so this order avoids scrolling through an ever-growing list of stable trees. Signed-off-by: Andreas Färber <afaerber@suse.de>
2012-04-13 17:52:27 +02:00
Stable 0.14
L: qemu-stable@nongnu.org
T: git git://git.qemu.org/qemu-stable-0.14.git
S: Orphan
Stable 0.10
L: qemu-stable@nongnu.org
T: git git://git.qemu.org/qemu-stable-0.10.git
S: Orphan
Reference in New Issue Copy Permalink