From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Dong Jia Shi <bjsdjshi@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PULL 0/1] vfio-ccw: another bugfix
Date: Fri, 27 Apr 2018 07:24:14 +0200 [thread overview]
Message-ID: <20180427072414.22118caa@mschwideX1> (raw)
In-Reply-To: <20180424112656.10243-1-cohuck@redhat.com>
On Tue, 24 Apr 2018 13:26:55 +0200
Cornelia Huck <cohuck@redhat.com> wrote:
> The following changes since commit 6cf09958f32b9667bb3ebadf74367c791112771b:
>
> s390: correct module section names for expoline code revert (2018-04-23 07:57:17 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git tags/vfio-ccw-20180424
>
> for you to fetch changes up to 427e522fc72395a4571b8dd7fe6d116927496bf7:
>
> vfio: ccw: fix cleanup if cp_prefetch fails (2018-04-23 14:11:20 +0200)
>
> ----------------------------------------------------------------
> Another vfio-ccw bug fix: Don't clean up things on error that were
> never translated in the first place.
>
> ----------------------------------------------------------------
>
> Halil Pasic (1):
> vfio: ccw: fix cleanup if cp_prefetch fails
>
> drivers/s390/cio/vfio_ccw_cp.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
Now added the s390/linux:fixes. Thanks.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2018-04-27 5:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 11:26 [PULL 0/1] vfio-ccw: another bugfix Cornelia Huck
2018-04-24 11:26 ` [PULL 1/1] vfio: ccw: fix cleanup if cp_prefetch fails Cornelia Huck
2018-04-27 5:24 ` Martin Schwidefsky [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=20180427072414.22118caa@mschwideX1 \
--to=schwidefsky@de.ibm.com \
--cc=bjsdjshi@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@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