From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: bjsdjshi@linux.vnet.ibm.com, pmorel@linux.vnet.ibm.com,
borntraeger@de.ibm.com, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] vfio-ccw: update documentation
Date: Tue, 16 Jan 2018 17:28:18 +0100 [thread overview]
Message-ID: <20180116172818.6f35a1c0.cohuck@redhat.com> (raw)
In-Reply-To: <5a99b7e2-3cce-c92d-f1d8-1469a334ff6d@linux.vnet.ibm.com>
On Tue, 16 Jan 2018 17:17:08 +0100
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
> On 01/15/2018 11:43 AM, Cornelia Huck wrote:
> > The vfio-ccw documentation comes from the cover letter of the
> > original patch submission, which shows in some parts. Give it some
> > love; in particular:
> >
> > - Remove/rework statements that make sense in a cover letter, but not
> > in regular documentation.
> > - Fix some typos.
> > - Describe the current limitations in more detail.
> >
> > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
>
> The changes look sane and definitively improve on what we have
> right now. Acked by me if you like.
Can you please give your explicit A-b on v2?
>
> When we are at the limitations, the prefetch story seems to be
> still missing. IMHO it's the most important limitation.
Yeah, that's just a start. I'm happy to take further patches :)
prev parent reply other threads:[~2018-01-16 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 10:43 [PATCH 0/1] vfio-ccw: start updating vfio-ccw.txt Cornelia Huck
2018-01-15 10:43 ` [PATCH 1/1] vfio-ccw: update documentation Cornelia Huck
[not found] ` <20180116065703.GF12499@bjsdjshi@linux.vnet.ibm.com>
2018-01-16 15:57 ` Cornelia Huck
2018-01-16 16:17 ` Halil Pasic
2018-01-16 16:28 ` 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=20180116172818.6f35a1c0.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.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