linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>,
	virtualization@lists.linux-foundation.org,
	linux-s390@vger.kernel.org, kvm@vger.kernel.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: separate section for s390 virtio drivers
Date: Wed, 1 Jul 2015 17:17:41 +0200	[thread overview]
Message-ID: <55940495.9050007@redhat.com> (raw)
In-Reply-To: <1435763737-10350-1-git-send-email-cornelia.huck@de.ibm.com>



On 01/07/2015 17:15, Cornelia Huck wrote:
> The s390-specific virtio drivers have probably more to do with virtio
> than with kvm today; let's move them out into a separate section to
> reflect this and to be able to add relevant mailing lists.
> 
> CC: Christian Borntraeger <borntraeger@de.ibm.com>
> Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> ---
>  MAINTAINERS | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 246d9d8..fca5c00 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5766,7 +5766,6 @@ S:	Supported
>  F:	Documentation/s390/kvm.txt
>  F:	arch/s390/include/asm/kvm*
>  F:	arch/s390/kvm/
> -F:	drivers/s390/kvm/
>  
>  KERNEL VIRTUAL MACHINE (KVM) FOR ARM
>  M:	Christoffer Dall <christoffer.dall@linaro.org>
> @@ -10671,6 +10670,15 @@ F:	drivers/block/virtio_blk.c
>  F:	include/linux/virtio_*.h
>  F:	include/uapi/linux/virtio_*.h
>  
> +VIRTIO DRIVERS FOR S390
> +M:	Christian Borntraeger <borntraeger@de.ibm.com>
> +M:	Cornelia Huck <cornelia.huck@de.ibm.com>
> +L:	linux-s390@vger.kernel.org
> +L:	virtualization@lists.linux-foundation.org
> +L:	kvm@vger.kernel.org

Keeping the KVM mailing list is probably a good idea.

> +S:	Supported
> +F:	drivers/s390/kvm/

Since we are at it, do we want to rename the directory to
drivers/s390/virtio?  Anyway:

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Paolo

>  VIRTIO HOST (VHOST)
>  M:	"Michael S. Tsirkin" <mst@redhat.com>
>  L:	kvm@vger.kernel.org
> 

  reply	other threads:[~2015-07-01 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 14:44 [PATCH 0/1] KVM: s390: virtio-ccw: Fix config space values Christian Borntraeger
2015-06-29 14:44 ` [PATCH 1/1] KVM: s390: virtio-ccw: don't overwrite " Christian Borntraeger
2015-07-01 13:36   ` Paolo Bonzini
2015-07-01 13:45 ` [PATCH 0/1] KVM: s390: virtio-ccw: Fix " Michael S. Tsirkin
2015-07-01 14:05   ` Paolo Bonzini
2015-07-01 14:18     ` Michael S. Tsirkin
2015-07-01 14:21       ` Paolo Bonzini
2015-07-01 15:15         ` [PATCH] MAINTAINERS: separate section for s390 virtio drivers Cornelia Huck
2015-07-01 15:17           ` Paolo Bonzini [this message]
2015-07-07  9:41             ` [PATCH] virtio/s390: rename drivers/s390/kvm -> drivers/s390/virtio Cornelia Huck
2015-07-07  9:44             ` [PATCH] MAINTAINERS: separate section for s390 virtio drivers Cornelia Huck
2015-07-07 11:19               ` Michael S. Tsirkin
2015-07-02  9:45           ` Christian Borntraeger

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=55940495.9050007@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

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

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