xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Harmandeep Kaur <write.harmandeep@gmail.com>,
	xen-devel@lists.xenproject.org
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com,
	ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] xl: Improve return and exit codes of parse_config_data().
Date: Tue, 23 Feb 2016 19:20:56 +0100	[thread overview]
Message-ID: <1456251656.17312.11.camel@citrix.com> (raw)
In-Reply-To: <1455899846-4146-1-git-send-email-write.harmandeep@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1291 bytes --]

On Fri, 2016-02-19 at 22:07 +0530, Harmandeep Kaur wrote:
> Turning parse_config_data() exit codes towards using the
> EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary
>
repetition of "instead of"

> numbers or libxl return codes.
>         - for main_*: arbitrary -> EXIT_SUCCESS|EXIT_FAILURE.
>         - for internal fucntion: arbitrary -> 0/1.
>
This is what you've done in other similar patches, and what should be
done in general. In the case of this patch, only one function is being
considered, and it's an internal void function, i.e., there's no
'internal returns', but only calls to exit().

This changelog should be made a little bit more specific, and say the
above (or maybe just leave the first paragraph there, and remove the
rest).

Apart from this, the code looks ok to me. So, with these changes, this
patch is:

> Signed-off-by: Harmandeep Kaur <write.harmandeep@gmail.com>
>
Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>

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

      reply	other threads:[~2016-02-23 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 16:37 [PATCH] xl: Improve return and exit codes of parse_config_data() Harmandeep Kaur
2016-02-23 18:20 ` Dario Faggioli [this message]

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=1456251656.17312.11.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.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).