From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: schwidefsky@de.ibm.com
Cc: bjsdjshi@linux.vnet.ibm.com, linux-s390@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PULL 0/2] Fixes for vfio-ccw
Date: Mon, 24 Apr 2017 10:53:34 +0200 [thread overview]
Message-ID: <20170424105334.7e1e37b9.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20170413105748.24092-1-cornelia.huck@de.ibm.com>
On Thu, 13 Apr 2017 12:57:46 +0200
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> The following changes since commit 1877888d0ad21858693d8a5594734b125a068638:
>
> MAINTAINERS: Add vfio-ccw maintainers (2017-03-31 12:55:12 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git tags/vfio-ccw-20170413
>
> for you to fetch changes up to 129cc19a94513081e9250323cd57e12ed48b3613:
>
> vfio: ccw: improve error handling for vfio_ccw_mdev_remove (2017-04-12 12:34:17 +0200)
>
> ----------------------------------------------------------------
> Two fixes for the new vfio-ccw support.
>
> ----------------------------------------------------------------
>
> Dong Jia Shi (2):
> vfio: ccw: remove unnecessary NULL checks of a pointer
> vfio: ccw: improve error handling for vfio_ccw_mdev_remove
>
> drivers/s390/cio/vfio_ccw_fsm.c | 6 +-----
> drivers/s390/cio/vfio_ccw_ops.c | 34 ++++++----------------------------
> 2 files changed, 7 insertions(+), 33 deletions(-)
>
ping
prev parent reply other threads:[~2017-04-24 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 10:57 [PULL 0/2] Fixes for vfio-ccw Cornelia Huck
2017-04-13 10:57 ` [PULL 1/2] vfio: ccw: remove unnecessary NULL checks of a pointer Cornelia Huck
2017-04-13 10:57 ` [PULL 2/2] vfio: ccw: improve error handling for vfio_ccw_mdev_remove Cornelia Huck
2017-04-24 8:53 ` Cornelia Huck [this message]
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=20170424105334.7e1e37b9.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.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