All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PULL 0/2] vfio-ccw: fixes
Date: Mon, 01 Oct 2018 14:12:03 +0000	[thread overview]
Message-ID: <20181001161203.0d9d2ff2@mschwideX1> (raw)
In-Reply-To: <20181001115358.5513-1-cohuck@redhat.com>

On Mon,  1 Oct 2018 13:53:56 +0200
Cornelia Huck <cohuck@redhat.com> wrote:

> The following changes since commit 55a5542a546238354d1f209f794414168cf8c71d:
> 
>   s390/hibernate: fix error handling when suspend cpu != resume cpu (2018-09-20 13:20:23 +0200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git tags/vfio-ccw-20181001
> 
> for you to fetch changes up to bf42daed6bd136774415ae6d26c8475152f92b54:
> 
>   s390/cio: Refactor alloc of ccw_io_region (2018-09-27 16:33:01 +0200)
> 
> ----------------------------------------------------------------
> Change allocation of ccw_io_region so that the usercopy hardening
> code can figure out that everything is fine.
> 
> ----------------------------------------------------------------
> 
> Eric Farman (2):
>   s390/cio: Convert ccw_io_region to pointer
>   s390/cio: Refactor alloc of ccw_io_region
> 
>  drivers/s390/cio/vfio_ccw_drv.c     | 24 +++++++++++++++++++++++-
>  drivers/s390/cio/vfio_ccw_fsm.c     |  6 +++---
>  drivers/s390/cio/vfio_ccw_ops.c     |  4 ++--
>  drivers/s390/cio/vfio_ccw_private.h |  2 +-
>  4 files changed, 29 insertions(+), 7 deletions(-)
> 

Pulled & pushed to linux-s390:fixes. Thanks.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

       reply	other threads:[~2018-10-01 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181001115358.5513-1-cohuck@redhat.com>
2018-10-01 14:12 ` Martin Schwidefsky [this message]
2017-10-16  9:50 [PULL 0/2] vfio-ccw fixes Cornelia Huck
2017-10-16 10:46 ` Martin Schwidefsky

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=20181001161203.0d9d2ff2@mschwideX1 \
    --to=schwidefsky@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.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.