All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
	Pierre Morel <pmorel@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] s390x/ccs: add ccw-tester emulated device
Date: Fri, 20 Oct 2017 17:46:42 +0200	[thread overview]
Message-ID: <20171020174642.7e045af4.cohuck@redhat.com> (raw)
In-Reply-To: <c17eb441-f22b-2e92-dd39-01c3caddec19@linux.vnet.ibm.com>

On Fri, 20 Oct 2017 16:33:47 +0200
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:

> OK, I will approach the z/VM guys. About EMULATED_CCW_3270_CHPID_TYPE,
> does it really make sense to have a separate chpid type for 3270? (You
> have missed that question, so I'm asking it again).

I had not. But my resources are depleted.

  reply	other threads:[~2017-10-20 15:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 13:27 [Qemu-devel] [PATCH 0/2] tests for CCW IDA Halil Pasic
2017-09-13 13:27 ` [Qemu-devel] [PATCH 1/2] s390x/ccs: add ccw-tester emulated device Halil Pasic
2017-09-14 14:26   ` Cornelia Huck
2017-09-14 16:50     ` Halil Pasic
2017-09-15  7:27       ` Cornelia Huck
2017-09-15 17:01         ` Cornelia Huck
2017-09-19 14:20           ` Pierre Morel
2017-09-25 15:06             ` Halil Pasic
2017-09-25 15:39               ` Cornelia Huck
2017-09-18  8:30         ` Christian Borntraeger
2017-09-18  8:42           ` Cornelia Huck
2017-10-19 16:39         ` Halil Pasic
2017-10-20 13:00           ` Cornelia Huck
2017-10-20 14:33             ` Halil Pasic
2017-10-20 15:46               ` Cornelia Huck [this message]
2017-09-19 14:26     ` Pierre Morel
2017-09-13 13:27 ` [Qemu-devel] [PATCH 2/2 NOT QEMU] a tester device for ccw I/O Halil Pasic

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=20171020174642.7e045af4.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=bjsdjshi@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=pmorel@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.