From: Eric Blake <eblake@redhat.com>
To: Quan Xu <quan.xu2@aliyun.com>, rea <emilcondrea@gmail.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"anthony.perard" <anthony.perard@citrix.com>
Cc: dgdegra <dgdegra@tycho.nsa.gov>,
xen-devel <xen-devel@lists.xen.org>,
"wei.liu2" <wei.liu2@citrix.com>,
qemu-devel <qemu-devel@nongnu.org>,
stefanb <stefanb@linux.vnet.ibm.com>
Subject: Re: [PATCH 01/19] xen: Create a new file xen_pvdev.c
Date: Mon, 18 Jul 2016 08:57:38 -0600 [thread overview]
Message-ID: <578CEE62.7010700@redhat.com> (raw)
In-Reply-To: <b45e5a51-c310-47fc-b417-d4aa5faea338.quan.xu2@aliyun.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1571 bytes --]
On 07/17/2016 01:41 AM, Quan Xu wrote:
>
> [Quan:]: comment starts with [Quan:]
>
This line doesn't belong in a commit message; it's fine to put it after
the --- separator though, if it aids mailing list reviewers.
>
> The purpose of the new file is to store generic functions shared by frontendand backends such as xenstore operations, xendevs.
>
s/frontendand/front end and/
Please wrap your commit message lines. Since 'git log' displays logs
with indentation, wrapping around 72 characters is ideal.
> Signed-off-by: Quan Xu <quan.xu@xxxxxxxxx>
> Signed-off-by: Emil Condrea <emilcondrea@xxxxxxxxx>
These are not valid S-o-b, therefore this patch cannot be applied as-is.
> -int xenstore_read_int(const char *base, const char *node, int *ival)
> -{
> - char *val;
> - int rc = -1;
> -
> - val = xenstore_read_str(base, node);
> [Quan:]: IMO, it is better to initialize val when declares. the same comment for the other 'val'
> - if (val && 1 == sscanf(val, "%d", ival)) {
This is not a valid patch. Are you replying to a patch that someone
else posted? If so, your quoting style is VERY difficult to read.
Please consider using a leading > before every line that you are quoting
(rather than pasting it verbatim as if you had written it), and include
a blank line both before and after every line that you insert, to call
visual attention to what is your reply vs. what you are quoting.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-18 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 7:41 [PATCH 01/19] xen: Create a new file xen_pvdev.c Quan Xu
2016-07-17 17:02 ` Emil Condrea
2016-07-18 14:50 ` Anthony PERARD
2016-07-18 14:57 ` Eric Blake [this message]
2016-07-18 16:54 ` Emil Condrea
2016-07-22 14:00 ` Quan Xu
[not found] <fc6b3ade-c945-4f0b-be73-f524c294ff99.quan.xu2@aliyun.com>
2016-07-22 14:28 ` Emil Condrea
-- strict thread matches above, loose matches on Subject: below --
2016-07-22 14:24 Quan Xu
[not found] <1468151270-12984-1-git-send-email-emilcondrea@gmail.com>
2016-07-10 11:47 ` Emil Condrea
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=578CEE62.7010700@redhat.com \
--to=eblake@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=emilcondrea@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=quan.xu2@aliyun.com \
--cc=sstabellini@kernel.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).