From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: Halil Pasic <pasic@linux.vnet.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
"Jason J . Herne" <jjherne@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/1] s390x: vmstatify config migration for virtio-ccw
Date: Tue, 6 Jun 2017 08:51:50 +0800 [thread overview]
Message-ID: <20170606005150.GB8262@bjsdjshi@linux.vnet.ibm.com> (raw)
In-Reply-To: <b912112c-7b34-3ba8-c1d4-308b84a06007@redhat.com>
* Eric Blake <eblake@redhat.com> [2017-06-05 07:19:14 -0500]:
Hi Eric,
> On 06/04/2017 10:09 PM, Dong Jia Shi wrote:
> > * Halil Pasic <pasic@linux.vnet.ibm.com> [2017-06-02 16:05:31 +0200]:
> >
> > Hi Halil,
> >
> > Sorry for the late show up. I just found some nits, which could be
> > ignored for me.
> >
> >> Let's vmstatify virtio_ccw_save_config and virtio_ccw_load_config for
> >> flexibility (extending using subsections) and for fun.
> >>
> >> To achieve this we need to hack the config_vector, which is VirtIODevice
> >> (that is common virtio) state, in the middle of the VirtioCcwDevice state
> >> representation. This is somewhat ugly, but we have no choice because the
> > ^^
> > Nit:-------------++
>
> What's wrong here? Two spaces between sentences is a common
> typographical convention
Thanks for letting me learn this. I didn't know this interesting
knowledge before I saw this comment and searched in the Internet:
https://en.wikipedia.org/wiki/Sentence_spacing
> (true, the codebase is inconsistent on whether sentences are separated
> with one or two spaces, but that's all the more reason to realize that
> since we don't have a consistent standard, it is just churn to change
> from one style to the other)
I was thinking 1) inconsistence is strange and unwelcome, and 2) the
inconsistence here may be something that Halil did not intend to have.
Since it's a common typographical convention, and I'm not a native
English speaker. I will follow your opinion.
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3266
> Virtualization: qemu.org | libvirt.org
>
--
Dong Jia Shi
next prev parent reply other threads:[~2017-06-06 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 14:05 [Qemu-devel] [PATCH v2 1/1] s390x: vmstatify config migration for virtio-ccw Halil Pasic
2017-06-05 3:09 ` Dong Jia Shi
2017-06-05 12:19 ` Eric Blake
2017-06-06 0:51 ` Dong Jia Shi [this message]
2017-06-06 8:21 ` Christian Borntraeger
2017-06-06 18:02 ` Halil Pasic
2017-06-06 18:07 ` Christian Borntraeger
2017-06-06 18:17 ` Halil Pasic
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=20170606005150.GB8262@bjsdjshi@linux.vnet.ibm.com \
--to=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@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).