From: Vasily Gorbik <gor@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PULL 0/1] vfio-ccw patch for next release
Date: Thu, 29 Aug 2019 16:38:39 +0200 [thread overview]
Message-ID: <your-ad-here.call-01567089519-ext-5685@work.hours> (raw)
In-Reply-To: <20190828155716.22809-1-cohuck@redhat.com>
On Wed, Aug 28, 2019 at 05:57:15PM +0200, Cornelia Huck wrote:
> The following changes since commit 416f79c23dbe47e0e223efc06d3487e1d90a92ee:
>
> s390/paes: Prepare paes functions for large key blobs (2019-08-21 12:58:54 +0200)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git tags/vfio-ccw-20190828
>
> for you to fetch changes up to 60e05d1cf0875f0cf73472f7dff71d9933c5b697:
>
> vfio-ccw: add some logging (2019-08-23 12:53:32 +0200)
>
> ----------------------------------------------------------------
> Add some logging into the s390dbf.
>
> ----------------------------------------------------------------
>
> Cornelia Huck (1):
> vfio-ccw: add some logging
>
> drivers/s390/cio/vfio_ccw_drv.c | 50 ++++++++++++++++++++++++++--
> drivers/s390/cio/vfio_ccw_fsm.c | 51 ++++++++++++++++++++++++++++-
> drivers/s390/cio/vfio_ccw_ops.c | 10 ++++++
> drivers/s390/cio/vfio_ccw_private.h | 17 ++++++++++
> 4 files changed, 124 insertions(+), 4 deletions(-)
>
> --
> 2.20.1
>
Applied, thanks!
--
⣿⣿⣿⣿⢋⡀⣀⠹⣿⣿⣿⣿
⣿⣿⣿⣿⠠⣶⡦⠀⣿⣿⣿⣿
⣿⣿⣿⠏⣴⣮⣴⣧⠈⢿⣿⣿
⣿⣿⡏⢰⣿⠖⣠⣿⡆⠈⣿⣿
⣿⢛⣵⣄⠙⣶⣶⡟⣅⣠⠹⣿
⣿⣜⣛⠻⢎⣉⣉⣀⠿⣫⣵⣿
prev parent reply other threads:[~2019-08-29 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 15:57 [PULL 0/1] vfio-ccw patch for next release Cornelia Huck
2019-08-28 15:57 ` [PULL 1/1] vfio-ccw: add some logging Cornelia Huck
2019-08-29 14:38 ` Vasily Gorbik [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=your-ad-here.call-01567089519-ext-5685@work.hours \
--to=gor@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@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