From: "Quan Xu" <quan.xu2@aliyun.com> To: Eric Blake <eblake@redhat.com>, Emil Condrea <emilcondrea@gmail.com> Cc: qemu-devel <qemu-devel@nongnu.org>, Daniel De Graaf <dgdegra@tycho.nsa.gov>, xen-devel <xen-devel@lists.xen.org>, Stefano Stabellini <sstabellini@kernel.org>, "wei.liu2" <wei.liu2@citrix.com>, stefanb <stefanb@linux.vnet.ibm.com>, "anthony.perard" <anthony.perard@citrix.com> Subject: Re: [Qemu-devel] [Xen-devel] [PATCH 01/19] xen: Create a new file xen_pvdev.c Date: Fri, 22 Jul 2016 22:00:40 +0800 [thread overview] Message-ID: <b33e4a25-f608-49e3-8072-ea28253680c3.quan.xu2@aliyun.com> (raw) In-Reply-To: CAAULxK+zqk0wVEkLUL2edn_qZ+MCQ+300RNHQyKO7E-xSvjvcw@mail.gmail.com sorry for the bad format from web email, and later review (neo training in new company).. patch 6 -- patch 12, rename * patch, are good to me. Quan ------------------------------------------------------------------From:Emil Condrea <emilcondrea@gmail.com>Time:2016 Jul 19 (Tue) 00:54To:Eric Blake <eblake@redhat.com>Cc:qemu-devel <qemu-devel@nongnu.org>; Daniel De Graaf <dgdegra@tycho.nsa.gov>; xen-devel <xen-devel@lists.xen.org>; Stefano Stabellini <sstabellini@kernel.org>; Quan Xu <quan.xu2@aliyun.com>; wei.liu2 <wei.liu2@citrix.com>; stefanb <stefanb@linux.vnet.ibm.com>; anthony.perard <anthony.perard@citrix.com>Subject:Re: [Xen-devel] [PATCH 01/19] xen: Create a new file xen_pvdev.c Eric, this is the link to the original patch which is well formatted: http://marc.info/?l=xen-devel&m=146815138831762&w=2I think that the formatting and s-o-b was broken in the reply from Quan.On Jul 18, 2016 17:57, "Eric Blake" <eblake@redhat.com> wrote: 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
WARNING: multiple messages have this Message-ID (diff)
From: "Quan Xu" <quan.xu2@aliyun.com> To: Eric Blake <eblake@redhat.com>, Emil Condrea <emilcondrea@gmail.com> Cc: Stefano Stabellini <sstabellini@kernel.org>, "wei.liu2" <wei.liu2@citrix.com>, stefanb <stefanb@linux.vnet.ibm.com>, qemu-devel <qemu-devel@nongnu.org>, xen-devel <xen-devel@lists.xen.org>, "anthony.perard" <anthony.perard@citrix.com>, Daniel De Graaf <dgdegra@tycho.nsa.gov> Subject: Re: [PATCH 01/19] xen: Create a new file xen_pvdev.c Date: Fri, 22 Jul 2016 22:00:40 +0800 [thread overview] Message-ID: <b33e4a25-f608-49e3-8072-ea28253680c3.quan.xu2@aliyun.com> (raw) In-Reply-To: CAAULxK+zqk0wVEkLUL2edn_qZ+MCQ+300RNHQyKO7E-xSvjvcw@mail.gmail.com [-- Attachment #1.1: Type: text/plain, Size: 2542 bytes --] sorry for the bad format from web email, and later review (neo training in new company).. patch 6 -- patch 12, rename * patch, are good to me. Quan ------------------------------------------------------------------From:Emil Condrea <emilcondrea@gmail.com>Time:2016 Jul 19 (Tue) 00:54To:Eric Blake <eblake@redhat.com>Cc:qemu-devel <qemu-devel@nongnu.org>; Daniel De Graaf <dgdegra@tycho.nsa.gov>; xen-devel <xen-devel@lists.xen.org>; Stefano Stabellini <sstabellini@kernel.org>; Quan Xu <quan.xu2@aliyun.com>; wei.liu2 <wei.liu2@citrix.com>; stefanb <stefanb@linux.vnet.ibm.com>; anthony.perard <anthony.perard@citrix.com>Subject:Re: [Xen-devel] [PATCH 01/19] xen: Create a new file xen_pvdev.c Eric, this is the link to the original patch which is well formatted: http://marc.info/?l=xen-devel&m=146815138831762&w=2I think that the formatting and s-o-b was broken in the reply from Quan.On Jul 18, 2016 17:57, "Eric Blake" <eblake@redhat.com> wrote: 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: Type: text/html, Size: 5129 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-22 14:07 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-07-17 7:41 [Qemu-devel] [Xen-devel] [PATCH 01/19] xen: Create a new file xen_pvdev.c Quan Xu 2016-07-17 7:41 ` Quan Xu 2016-07-17 17:02 ` Emil Condrea 2016-07-17 17:02 ` [Qemu-devel] [Xen-devel] " Emil Condrea 2016-07-18 14:50 ` Anthony PERARD 2016-07-18 14:50 ` [Qemu-devel] [Xen-devel] " Anthony PERARD 2016-07-18 14:57 ` Eric Blake 2016-07-18 14:57 ` Eric Blake 2016-07-18 16:54 ` Emil Condrea 2016-07-18 16:54 ` [Qemu-devel] [Xen-devel] " Emil Condrea 2016-07-22 14:00 ` Quan Xu [this message] 2016-07-22 14:00 ` Quan Xu 2016-07-22 14:24 [Qemu-devel] [Xen-devel] " Quan Xu 2016-07-22 14:28 ` 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=b33e4a25-f608-49e3-8072-ea28253680c3.quan.xu2@aliyun.com \ --to=quan.xu2@aliyun.com \ --cc=anthony.perard@citrix.com \ --cc=dgdegra@tycho.nsa.gov \ --cc=eblake@redhat.com \ --cc=emilcondrea@gmail.com \ --cc=qemu-devel@nongnu.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.