qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org, thuth@redhat.com,
	david@redhat.com, agraf@suse.de, borntraeger@de.ibm.com,
	rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 1/3] MAINTAINERS: add myself as overall s390x maintainer
Date: Wed, 7 Feb 2018 17:28:27 +0100	[thread overview]
Message-ID: <20180207172827.6af1486b.cohuck@redhat.com> (raw)
In-Reply-To: <5b0fccea-dce9-ebc9-4f9e-995056d84fe3@amsat.org>

On Wed, 7 Feb 2018 13:24:09 -0300
Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:

> On 02/07/2018 12:55 PM, Cornelia Huck wrote:
> > All your mainframes are belong to me.  
> 
> =)
> 
> > 
> > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> > ---
> >  MAINTAINERS | 23 +++++++++++++++++++++++
> >  1 file changed, 23 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index bbc3a617c2..e24273a574 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -76,6 +76,29 @@ K: ^Subject:.*(?i)trivial
> >  T: git git://git.corpit.ru/qemu.git trivial-patches
> >  T: git git://github.com/vivier/qemu.git trivial-patches
> >  
> > +Architecture support
> > +--------------------
> > +S390
> > +M: Cornelia Huck <cohuck@redhat.com>
> > +S: Supported
> > +F: default-configs/s390x-softmmu.mak
> > +F: gdb-xml/s390*.xml
> > +F: hw/char/sclp*.[hc]
> > +F: hw/char/terminal3270.c
> > +F: hw/intc/s390_flic.c
> > +F: hw/intc/s390_flic_kvm.c
> > +F: hw/s390x/
> > +F: hw/vfio/ccw.c
> > +F: hw/watchdog/wdt_diag288.c
> > +F: include/hw/s390x/
> > +F: include/hw/watchdog/wdt_diag288.h
> > +F: pc-bios/s390-ccw/
> > +F: pc-bios/s390-ccw.img
> > +F: target/s390x/
> > +K: ^Subject:.*(?i)s390(x|)  
> 
> (x|) -> x?

Probably (my perl regexp fu is very lacking).

> 
> > +T: git git://github.com/cohuck/qemu.git s390-next
> > +L: qemu-s390x@nongnu.org
> > +
> >  Guest CPU cores (TCG):
> >  ----------------------
> >  Overall
> >   
> 
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

Thanks!

  reply	other threads:[~2018-02-07 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 15:55 [Qemu-devel] [PATCH 0/3] s390x: maintainership reorg Cornelia Huck
2018-02-07 15:55 ` [Qemu-devel] [PATCH 1/3] MAINTAINERS: add myself as overall s390x maintainer Cornelia Huck
2018-02-07 16:24   ` Philippe Mathieu-Daudé
2018-02-07 16:28     ` Cornelia Huck [this message]
2018-02-07 18:19   ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-02-08 12:17   ` [Qemu-devel] " David Hildenbrand
2018-02-08 15:25   ` Daniel Henrique Barboza
2018-02-07 15:55 ` [Qemu-devel] [PATCH 2/3] MAINTAINERS: reorganize s390-ccw bios maintainership Cornelia Huck
2018-02-07 18:21   ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-02-07 18:47   ` [Qemu-devel] " Thomas Huth
2018-02-07 15:55 ` [Qemu-devel] [PATCH 3/3] MAINTAINERS: add David as additional tcg/s390 maintainer Cornelia Huck
2018-02-08 12:09   ` David Hildenbrand
2018-02-08 15:14 ` [Qemu-devel] [PATCH 0/3] s390x: maintainership reorg Cornelia Huck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180207172827.6af1486b.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).