From: Dario Faggioli <dario.faggioli@citrix.com>
To: Harmandeep Kaur <write.harmandeep@gmail.com>,
xen-devel@lists.xenproject.org
Cc: lars.kurth@citrix.com, wei.liu2@citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
ian.jackson@eu.citrix.com, george.dunlap@citrix.com
Subject: Re: [PATCH v2 5/5] xl: improve return and exit codes of parse related functions
Date: Mon, 26 Oct 2015 11:40:28 +0100 [thread overview]
Message-ID: <1445856028.2717.57.camel@citrix.com> (raw)
In-Reply-To: <1445664696-14258-6-git-send-email-write.harmandeep@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1528 bytes --]
On Sat, 2015-10-24 at 11:01 +0530, Harmandeep Kaur wrote:
> turning parsing related functions xl exit codes towards using the
> EXIT_[SUCCESS|FAILURE] macros, instead of instead of arbitrary
> numbers
> or libxl return codes.
>
> it doesn't include parse_config_data() which is big enough to deserve
> its
> own patch
>
> Signed-off-by: Harmandeep Kaur <write.harmandeep@gmail.com>
> libxl_bitmap *cpumap)
> static int cpurange_parse(const char *cpu, libxl_bitmap *cpumap)
> {
> char *ptr, *saveptr = NULL, *buf = strdup(cpu);
> - int rc = 0;
>
> for (ptr = strtok_r(buf, ",", &saveptr); ptr;
> ptr = strtok_r(NULL, ",", &saveptr)) {
> - rc = update_cpumap_range(ptr, cpumap);
> - if (rc)
> + if (update_cpumap_range(ptr, cpumap))
> break;
> }
> free(buf);
>
> - return rc;
> + return 0;
> }
>
Oh, and also, here: I think rc is needed, in this case, to properly
deal with the failure of update_cpumap_range(), and poperly propagate
that failure to the caller.
If you want to get rid of it, you should do something like this, inside
the loop:
if (update_cpumap_range(ptr, cpumap)) {
free(buf);
return 1;
}
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-26 10:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 5:31 [PATCH v2 0/5] xl: convert exit codes to EXIT_[SUCCESS|FAILURE] Harmandeep Kaur
2015-10-24 5:31 ` [PATCH v2 1/5] " Harmandeep Kaur
2015-10-26 9:32 ` Dario Faggioli
2015-10-26 17:39 ` Wei Liu
2015-10-24 5:31 ` [PATCH v2 2/5] xl: improve return and exit codes of scheduling related functions Harmandeep Kaur
2015-10-26 9:56 ` Dario Faggioli
2015-10-24 5:31 ` [PATCH v2 3/5] xl: improve return and exit codes of vcpu " Harmandeep Kaur
2015-10-26 10:03 ` Dario Faggioli
2015-10-24 5:31 ` [PATCH v2 4/5] xl: improve return and exit codes of cpupool " Harmandeep Kaur
2015-10-26 10:06 ` Dario Faggioli
2015-10-24 5:31 ` [PATCH v2 5/5] xl: improve return and exit codes of parse " Harmandeep Kaur
2015-10-26 10:34 ` Dario Faggioli
2015-10-26 10:40 ` Dario Faggioli [this message]
2015-10-26 17:54 ` Wei Liu
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=1445856028.2717.57.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).