qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: xiezhide <xiezhide@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "groug@kaod.org" <groug@kaod.org>,
	"aneesh.kumar@linux.vnet.ibm.com"
	<aneesh.kumar@linux.vnet.ibm.com>,
	"armbru@redhat.com" <armbru@redhat.com>,
	"berto@igalia.com" <berto@igalia.com>,
	zengcanfu 00215970 <zengcanfu@huawei.com>,
	Jinxuefeng <jinxuefeng@huawei.com>,
	"Chenhui (Felix, Euler)" <chenhui.rtos@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v4 2/4] fsdev-throttle-qmp: move struct ThrottleLimits to new file
Date: Fri, 16 Nov 2018 09:03:20 -0600	[thread overview]
Message-ID: <c2c4e7d2-b39f-1d82-f382-4aab96c9ee2a@redhat.com> (raw)
In-Reply-To: <A02D6AA901860840B46E751C5E9E38B43CC975D8@DGGEML532-MBX.china.huawei.com>

On 11/16/18 2:21 AM, xiezhide wrote:
> 

Here's a couple of meta observations:


> 
>>
>> Signed-off-by: xiezhide <xiezhide@huawei.com>

Your sign-off line ...[1]

>> -    if (arg->has_bps_total) {
>> -        cfg->buckets[THROTTLE_BPS_TOTAL].avg = arg->bps_total;
>> +    if (arg->has_bps) {
>> +        cfg->buckets[THROTTLE_BPS_TOTAL].avg = arg->bps;
> 
> Otherwise, the churn from renaming members (part 1) makes it hard to see if the code was properly moved into a new file.
> 
> Split this patch to three patches in v5

Your mailer's quoting style makes it very hard to read your replies. 
You are including both a line that I originally wrote and your reply 
with no difference in quoting levels between the two, which makes it 
look like you are writing both the question and the answer.  It is MUCH 
easier to read mails where quoted material is prefixed by some form of 
quoting (and '>' is probably the easiest form).

> 
> Thanks
> Kidd

[1] ...does not match your informal signature.  That's not necessarily a 
problem, but the project does prefer that Signed-off-by lines use a 
preferred legal name rather than merely a nickname or username.  It is 
acceptable for a sign off to include multiple variations of your name 
(I've seen people use UTF-8 characters to represent their name natively, 
followed by a Latinized transcription of the name they use in English), 
as well as signatures that use just a UTF-8 form or just a Latinized 
form; at the same time, I won't reject your patch as written, because if 
you look hard enough in git history, you'll find other commit authors 
that got away with a username or nickname.  If you prefer to be 
addressed by 'Kidd' when speaking in English, then including that as 
part of your S-o-b lines will help other reviewers know the best name to 
use for mentioning you by name.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-11-16 15:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15  8:54 [Qemu-devel] [PATCH v4 0/4] fsdev-throttle-qmp: qmp interface for fsdev io throttling xiezhide
2018-11-15  8:54 ` [Qemu-devel] [PATCH v4 1/4] fsdev-throttle-qmp: factor out throttle code to reuse code xiezhide
2018-11-15 20:55   ` Eric Blake
2018-11-16  8:24     ` xiezhide
2018-11-15  8:55 ` [Qemu-devel] [PATCH v4 2/4] fsdev-throttle-qmp: move struct ThrottleLimits to new file xiezhide
2018-11-15 21:41   ` Eric Blake
2018-11-15 22:02     ` Eric Blake
2018-11-16  8:19       ` xiezhide
2018-11-16  8:21     ` xiezhide
2018-11-16 15:03       ` Eric Blake [this message]
2018-11-15  8:55 ` [Qemu-devel] [PATCH v4 3/4] fsdev-throttle-qmp: qmp interface for fsdev io throttling xiezhide
2018-11-15  8:55 ` [Qemu-devel] [PATCH v4 4/4] fsdev-throttle-qmp: hmp " xiezhide

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=c2c4e7d2-b39f-1d82-f382-4aab96c9ee2a@redhat.com \
    --to=eblake@redhat.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=berto@igalia.com \
    --cc=chenhui.rtos@huawei.com \
    --cc=groug@kaod.org \
    --cc=jinxuefeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xiezhide@huawei.com \
    --cc=zengcanfu@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).