From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PULL 0/1] vfio-ccw: another bugfix
Date: Mon, 08 Oct 2018 07:20:20 +0000 [thread overview]
Message-ID: <20181008092020.0b86f3b2@mschwideX1> (raw)
In-Reply-To: <20181002153748.13503-1-cohuck@redhat.com>
On Tue, 2 Oct 2018 17:37:47 +0200
Cornelia Huck <cohuck@redhat.com> wrote:
> [Sorry about that; I don't plan to make this a daily thing...]
>
> The following changes since commit c458dda3d07c110ce1d007998f67273325ad8662:
>
> Merge tag 'vfio-ccw-20181001' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw into fixes (2018-10-01 16:07:42 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git tags/vfio-ccw-20181002
>
> for you to fetch changes up to 24abf2901b18bf941b9f21ea2ce5791f61097ae4:
>
> s390/cio: Fix how vfio-ccw checks pinned pages (2018-10-02 09:45:05 +0200)
>
> ----------------------------------------------------------------
> Another fix for vfio-ccw: make sure it accesses the correct entries
> in the pfn_array_table arrays when checking pinned pages.
>
> ----------------------------------------------------------------
>
> Eric Farman (1):
> s390/cio: Fix how vfio-ccw checks pinned pages
>
> drivers/s390/cio/vfio_ccw_cp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Pulled and push to linux-s390:fixes. I'll wait for a couple of days
before I send a please pull to Greg with the fixes.
Thanks.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2018-10-08 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181002153748.13503-1-cohuck@redhat.com>
2018-10-02 15:37 ` [PULL 1/1] s390/cio: Fix how vfio-ccw checks pinned pages Cornelia Huck
2018-10-03 13:14 ` Farhan Ali
2018-10-08 7:20 ` Martin Schwidefsky [this message]
2018-04-24 11:26 [PULL 0/1] vfio-ccw: another bugfix Cornelia Huck
2018-04-27 5:24 ` 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=20181008092020.0b86f3b2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox