From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
Harmandeep Kaur <write.harmandeep@gmail.com>
Cc: lars.kurth@citrix.com, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
george.dunlap@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 2/5] xl: improve return and exit codes of scheduling related functions
Date: Tue, 27 Oct 2015 15:30:22 +0100 [thread overview]
Message-ID: <1445956222.2937.155.camel@citrix.com> (raw)
In-Reply-To: <20151027135032.GV18674@zion.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1470 bytes --]
On Tue, 2015-10-27 at 13:50 +0000, Wei Liu wrote:
> On Tue, Oct 27, 2015 at 06:18:55PM +0530, Harmandeep Kaur wrote:
> > diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
> > index 646b281..b101aff 100644
> > --- a/tools/libxl/xl_cmdimpl.c
> > +++ b/tools/libxl/xl_cmdimpl.c
> > @@ -5793,18 +5793,15 @@ int main_sharing(int argc, char **argv)
> > static int sched_domain_get(libxl_scheduler sched, int domid,
> > libxl_domain_sched_params *scinfo)
> > {
> > - int rc;
> > -
> > - rc = libxl_domain_sched_params_get(ctx, domid, scinfo);
> > - if (rc) {
> > + if (libxl_domain_sched_params_get(ctx, domid, scinfo)){
>
> This, and other instances in both patch 2 and 3, violates coding
> style.
> You need to have a space before "{".
>
Bha, I guess I was concentrating on the "return / exit()" changes, and
managed to miss these! :-/
> After that, you can add my ack to all your patches. I haven't
> carefully
> read through every line of change, but I think Dario's review is
> sufficient
> and thorough.
>
And yet, I managed to miss those coding style issues. :-(
> Thanks Dario.
>
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-10-27 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 12:48 [PATCH v4 0/5] xl: convert exit codes to EXIT_[SUCCESS|FAILURE] Harmandeep Kaur
2015-10-27 12:48 ` [PATCH v4 1/5] xl: convert main() " Harmandeep Kaur
2015-10-27 12:48 ` [PATCH v4 2/5] xl: improve return and exit codes of scheduling related functions Harmandeep Kaur
2015-10-27 13:50 ` Wei Liu
2015-10-27 14:30 ` Dario Faggioli [this message]
2015-10-27 12:48 ` [PATCH v4 3/5] xl: improve return and exit codes of vcpu " Harmandeep Kaur
2015-10-27 12:48 ` [PATCH v4 4/5] xl: improve return and exit codes of cpupool " Harmandeep Kaur
2015-10-27 12:48 ` [PATCH v4 5/5] xl: improve return and exit codes of parse " Harmandeep Kaur
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=1445956222.2937.155.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=lars.kurth@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=write.harmandeep@gmail.com \
--cc=xen-devel@lists.xenproject.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).