qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
	qemu-s390x@nongnu.org,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-3.1 00/10] Move virtio-ccw devices to separate files
Date: Wed, 15 Aug 2018 13:45:18 +0200	[thread overview]
Message-ID: <20180815134518.19cea8e5.cohuck@redhat.com> (raw)
In-Reply-To: <1532521224-27235-1-git-send-email-thuth@redhat.com>

On Wed, 25 Jul 2018 14:20:14 +0200
Thomas Huth <thuth@redhat.com> wrote:

> For more fine-grained control over the build process, it would be good
> to have the possibility to disable single virtio devices, too. We already
> have CONFIG_VIRTIO_* switches in the Makefiles, but currently all
> virtio-ccw devices are compiled in anyway. Move them to separate files
> so we can disable them in the Makefile more easily.
> 
> NB: I did not move virtio-blk-ccw and virtio-net-ccw to a separate file
> yet since they are essential for the s390x-virtio machine and thus it
> does IMHO not make much sense to disable net and blk. But if somebody
> needs that possibility, too, I can add two more patches on top...
> 
> Thomas Huth (10):
>   hw/s390x/virtio-ccw: Consolidate calls to virtio_ccw_unrealize()
>   hw/s390x: Move virtio-ccw-serial code to a separate file
>   hw/s390x: Move virtio-ccw-balloon code to a separate file
>   hw/s390x: Move virtio-ccw-scsi code to a separate file
>   hw/s390x: Move virtio-ccw-rng code to a separate file
>   hw/s390x: Move virtio-ccw-9p code to a separate file
>   hw/s390x: Move virtio-ccw-crypto code to a separate file
>   hw/s390x: Move vhost-vsock-ccw code to a separate file
>   hw/s390x: Move virtio-ccw-gpu code to a separate file
>   hw/s390x: Move virtio-ccw-input code to a separate file
> 
>  MAINTAINERS                   |   2 +-
>  hw/s390x/Makefile.objs        |   9 +
>  hw/s390x/vhost-vsock-ccw.c    |  60 +++++
>  hw/s390x/virtio-ccw-9p.c      |  65 +++++
>  hw/s390x/virtio-ccw-balloon.c |  70 +++++
>  hw/s390x/virtio-ccw-crypto.c  |  75 ++++++
>  hw/s390x/virtio-ccw-gpu.c     |  67 +++++
>  hw/s390x/virtio-ccw-input.c   | 118 +++++++++
>  hw/s390x/virtio-ccw-rng.c     |  74 ++++++
>  hw/s390x/virtio-ccw-scsi.c    | 125 +++++++++
>  hw/s390x/virtio-ccw-serial.c  |  78 ++++++
>  hw/s390x/virtio-ccw.c         | 581 +-----------------------------------------
>  12 files changed, 749 insertions(+), 575 deletions(-)
>  create mode 100644 hw/s390x/vhost-vsock-ccw.c
>  create mode 100644 hw/s390x/virtio-ccw-9p.c
>  create mode 100644 hw/s390x/virtio-ccw-balloon.c
>  create mode 100644 hw/s390x/virtio-ccw-crypto.c
>  create mode 100644 hw/s390x/virtio-ccw-gpu.c
>  create mode 100644 hw/s390x/virtio-ccw-input.c
>  create mode 100644 hw/s390x/virtio-ccw-rng.c
>  create mode 100644 hw/s390x/virtio-ccw-scsi.c
>  create mode 100644 hw/s390x/virtio-ccw-serial.c
> 

Trawling through my backlog... I don't think there were any issues with
this? I think I'll just go ahead and queue this (would not mind
reviews, though).

  parent reply	other threads:[~2018-08-15 11:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 12:20 [Qemu-devel] [PATCH for-3.1 00/10] Move virtio-ccw devices to separate files Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 01/10] hw/s390x/virtio-ccw: Consolidate calls to virtio_ccw_unrealize() Thomas Huth
2018-07-26  9:15   ` Cornelia Huck
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 02/10] hw/s390x: Move virtio-ccw-serial code to a separate file Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 03/10] hw/s390x: Move virtio-ccw-balloon " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 04/10] hw/s390x: Move virtio-ccw-scsi " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 05/10] hw/s390x: Move virtio-ccw-rng " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 06/10] hw/s390x: Move virtio-ccw-9p " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 07/10] hw/s390x: Move virtio-ccw-crypto " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 08/10] hw/s390x: Move vhost-vsock-ccw " Thomas Huth
2018-08-23 14:13   ` Cornelia Huck
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 09/10] hw/s390x: Move virtio-ccw-gpu " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 10/10] hw/s390x: Move virtio-ccw-input " Thomas Huth
2018-07-25 13:48 ` [Qemu-devel] [PATCH for-3.1 00/10] Move virtio-ccw devices to separate files Cornelia Huck
2018-07-25 17:20   ` Thomas Huth
2018-07-26  9:07     ` Cornelia Huck
2018-07-25 13:52 ` Christian Borntraeger
2018-07-25 16:21   ` Juan Quintela
2018-07-25 17:15     ` Thomas Huth
2018-07-25 18:07 ` [Qemu-devel] [PATCH for-3.1 11/10] hw/s390x: Move virtio-ccw-net code to a separate file Thomas Huth
2018-07-25 18:08 ` [Qemu-devel] [PATCH for-3.1 12/10] hw/s390x: Move virtio-ccw-blk " Thomas Huth
2018-08-15 11:45 ` Cornelia Huck [this message]
2018-08-23 14:25 ` [Qemu-devel] [PATCH for-3.1 00/10] Move virtio-ccw devices to separate files 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=20180815134518.19cea8e5.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=quintela@redhat.com \
    --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).