From: Tony Krowiak <akrowiak@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
borntraeger@de.ibm.com, david@redhat.com, pmorel@linux.ibm.com,
alifm@linux.ibm.com, mjrosato@linux.ibm.com, pasic@linux.ibm.com,
alex.williamson@redhat.com, fiuczy@linux.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 2/2] s390x/vfio-ap: document hot plug/unplug of vfio-ap device
Date: Thu, 21 Feb 2019 11:26:53 -0500 [thread overview]
Message-ID: <ee4e057a-8c40-1c40-3fbe-acbe4cc64aab@linux.ibm.com> (raw)
In-Reply-To: <20190220165128.630ad793.cohuck@redhat.com>
On 2/20/19 10:51 AM, Cornelia Huck wrote:
> On Mon, 18 Feb 2019 14:49:57 -0500
> Tony Krowiak <akrowiak@linux.ibm.com> wrote:
>
>> Let's update the vfio-ap.txt document to include the hot plug/unplug
>> support introduced in this patch set.
>
> s/ introduced in this patch set//
>
> Nobody will know about this patch set when they look at the commit in
> the future :)
Good point, I'll remove it.
>
>>
>> Signed-off-by: Tony Krowiak <akrowiak@linux.ibm.com>
>> ---
>> docs/vfio-ap.txt | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++-----
>> 1 file changed, 56 insertions(+), 5 deletions(-)
>
> Looks good to me, but would not mind a R-b before queuing.
>
next prev parent reply other threads:[~2019-02-21 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 19:49 [Qemu-devel] [PATCH v3 0/2] s390x/vfio-ap: hot plug/unplug vfio-ap device Tony Krowiak
2019-02-18 19:49 ` [Qemu-devel] [PATCH v3 1/2] s390x/vfio-ap: Implement hot plug/unplug of " Tony Krowiak
2019-02-18 19:49 ` [Qemu-devel] [PATCH v3 2/2] s390x/vfio-ap: document " Tony Krowiak
2019-02-20 15:51 ` Cornelia Huck
2019-02-21 16:26 ` Tony Krowiak [this message]
2019-02-21 16:32 ` Cornelia Huck
2019-03-11 14:36 ` Tony Krowiak
2019-02-25 12:42 ` [Qemu-devel] [PATCH v3 0/2] s390x/vfio-ap: hot plug/unplug " Cornelia Huck
2019-03-11 14:37 ` Tony Krowiak
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=ee4e057a-8c40-1c40-3fbe-acbe4cc64aab@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=fiuczy@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.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;
as well as URLs for NNTP newsgroup(s).