All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Farman <farman@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	Farhan Ali <alifm@linux.ibm.com>,
	Pierre Morel <pmorel@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, qemu-s390x@nongnu.org,
	Alex Williamson <alex.williamson@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH v3 0/2] vfio-ccw: support hsch/csch (QEMU part)
Date: Thu, 21 Mar 2019 21:49:54 -0400	[thread overview]
Message-ID: <7c196819-c0b1-9c8d-b43d-786189c82cac@linux.ibm.com> (raw)
In-Reply-To: <20190301093949.27955-1-cohuck@redhat.com>



On 3/1/19 4:39 AM, Cornelia Huck wrote:
> 
> [I'm not quite happy with how this async processing hooks up in css.c;
> ideas welcome.]

I guess I'm not unhappy with it, but it does look a little odd.  Not 
sure I have a better idea right now...  Will ponder that for a while.

  - Eric

  parent reply	other threads:[~2019-03-22  1:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01  9:39 [PATCH v3 0/2] vfio-ccw: support hsch/csch (QEMU part) Cornelia Huck
2019-03-01  9:39 ` [Qemu-devel] " Cornelia Huck
2019-03-01  9:39 ` [PATCH v3 1/2] vfio-ccw: new capability chain support Cornelia Huck
2019-03-01  9:39   ` [Qemu-devel] " Cornelia Huck
2019-03-21 20:19   ` Eric Farman
2019-03-01  9:39 ` [PATCH v3 2/2] vfio-ccw: support async command subregion Cornelia Huck
2019-03-01  9:39   ` [Qemu-devel] " Cornelia Huck
2019-03-22  1:38   ` Eric Farman
2019-04-02 13:42     ` Cornelia Huck
2019-04-02 13:42       ` [Qemu-devel] " Cornelia Huck
2019-03-22  1:49 ` Eric Farman [this message]
2019-04-02 13:44   ` [PATCH v3 0/2] vfio-ccw: support hsch/csch (QEMU part) Cornelia Huck
2019-04-02 13:44     ` [Qemu-devel] " 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=7c196819-c0b1-9c8d-b43d-786189c82cac@linux.ibm.com \
    --to=farman@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=alifm@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.com \
    --cc=pmorel@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@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.