From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Jay Zhou <jianjay.zhou@huawei.com>,
qemu-devel@nongnu.org, quintela@redhat.com,
weidong.huang@huawei.com, wangxinxin.wang@huawei.com
Subject: Re: [Qemu-devel] [PATCH] docs/devel/migration.txt: keep functions consistent with the code
Date: Fri, 15 Dec 2017 12:21:39 +0000 [thread overview]
Message-ID: <20171215122139.GC11724@redhat.com> (raw)
In-Reply-To: <20171205195816.GH2405@work-vm>
On Tue, Dec 05, 2017 at 07:58:16PM +0000, Dr. David Alan Gilbert wrote:
> * Jay Zhou (jianjay.zhou@huawei.com) wrote:
> > Since the commit 11808bb0c422134bf09119f4aa22c59b0ce84bf3 removed
> > the put_buffer callback and using an iovec based write handler instead,
> > the docs should be sync with the code too.
> >
> > Signed-off-by: Jay Zhou <jianjay.zhou@huawei.com>
>
> Lets check with Dan (added to cc) since he wrote 11808bb;
> it might be best just to rever to migration/qemu-file.h for an
> explanation of each function.
The updates look ok, but I tend to think this entire section of
migrate.txt should be deleted, in favour of the inline APIs
docs in mijgration/qemu-file.h As a developer the header file
is where I would look for this kind of API description. The
migration.txt can just point epople to the header file for API
docs.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-12-15 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 8:47 [Qemu-devel] [PATCH] docs/devel/migration.txt: keep functions consistent with the code Jay Zhou
2017-11-23 9:15 ` no-reply
2017-11-24 1:05 ` Jay Zhou
2017-11-24 9:46 ` Dr. David Alan Gilbert
2017-12-05 2:18 ` Jay Zhou
2017-12-05 19:58 ` Dr. David Alan Gilbert
2017-12-15 12:21 ` Daniel P. Berrange [this message]
2017-12-15 15:15 ` Dr. David Alan Gilbert
2017-12-18 1:36 ` Zhoujian (jay)
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=20171215122139.GC11724@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jianjay.zhou@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.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;
as well as URLs for NNTP newsgroup(s).