public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Farhan Ali <alifm@linux.ibm.com>
Cc: Eric Farman <farman@linux.ibm.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	Pierre Morel <pmorel@linux.ibm.com>,
	linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v3 0/3] s390: vfio-ccw fixes
Date: Thu, 23 May 2019 08:32:06 +0200	[thread overview]
Message-ID: <20190523083206.07e374bf.cohuck@redhat.com> (raw)
In-Reply-To: <0769d5bc-cf0b-3a66-7d35-381490a115b5@linux.ibm.com>

On Wed, 22 May 2019 08:20:43 -0400
Farhan Ali <alifm@linux.ibm.com> wrote:

> On 05/16/2019 12:14 PM, Eric Farman wrote:
> > Here are the remaining patches in my fixes series, to handle the more
> > involved scenario of channel programs that do not move any actual data
> > to/from the device.  They were reordered per feedback from v2, which
> > means they received minor massaging because of overlapping code and
> > some cleanup to the commit messages.
> > 
> > They are based on Conny's vfio-ccw tree.  :)
> > 
> > Changelog:
> >   v2 -> v3:
> >    - Patches 1-4:
> >       - [Farhan] Added r-b
> >       - [Cornelia] Queued to vfio-ccw, dropped from this version
> >    - Patches 5/6:
> >       - [Cornelia/Farhan] Swapped the order of these patches, minor
> >         rework on the placement of bytes/idaw_nr variables and the
> >         commit messages that resulted.
> >   v2: https://patchwork.kernel.org/cover/10944075/
> >   v1: https://patchwork.kernel.org/cover/10928799/
> > 
> > Eric Farman (3):
> >    s390/cio: Don't pin vfio pages for empty transfers
> >    s390/cio: Allow zero-length CCWs in vfio-ccw
> >    s390/cio: Remove vfio-ccw checks of command codes
> > 
> >   drivers/s390/cio/vfio_ccw_cp.c | 92 ++++++++++++++++++++++++----------
> >   1 file changed, 65 insertions(+), 27 deletions(-)
> >   
> 
> 
> Acked-by: Farhan Ali <alifm@linux.ibm.com> for the series.

Thank you!

  reply	other threads:[~2019-05-23  6:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 16:14 [PATCH v3 0/3] s390: vfio-ccw fixes Eric Farman
2019-05-16 16:14 ` [PATCH v3 1/3] s390/cio: Don't pin vfio pages for empty transfers Eric Farman
2019-05-17  9:06   ` Cornelia Huck
2019-05-17 12:57     ` Eric Farman
2019-05-17 14:06       ` Cornelia Huck
2019-05-17 14:20         ` Eric Farman
2019-05-20 20:35   ` Farhan Ali
2019-05-21  2:29     ` Eric Farman
2019-05-16 16:14 ` [PATCH v3 2/3] s390/cio: Allow zero-length CCWs in vfio-ccw Eric Farman
2019-05-16 16:14 ` [PATCH v3 3/3] s390/cio: Remove vfio-ccw checks of command codes Eric Farman
2019-05-22 12:20 ` [PATCH v3 0/3] s390: vfio-ccw fixes Farhan Ali
2019-05-23  6:32   ` Cornelia Huck [this message]
2019-05-23  6:44 ` 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=20190523083206.07e374bf.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alifm@linux.ibm.com \
    --cc=farman@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.com \
    --cc=pmorel@linux.ibm.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