xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Harmandeep Kaur <write.harmandeep@gmail.com>,
	xen-devel@lists.xenproject.org
Cc: lars.kurth@citrix.com, wei.liu2@citrix.com,
	stefano.stabellini@eu.citrix.com, dario.faggioli@citrix.com,
	ian.jackson@eu.citrix.com, george.dunlap@citrix.com
Subject: Re: [PATCH v6 0/5] xl: convert exit codes to EXIT_[SUCCESS|FAILURE]
Date: Wed, 4 Nov 2015 09:40:18 +0000	[thread overview]
Message-ID: <1446630018.16178.69.camel@citrix.com> (raw)
In-Reply-To: <1445999184-4950-1-git-send-email-write.harmandeep@gmail.com>

On Wed, 2015-10-28 at 07:56 +0530, Harmandeep Kaur wrote:

All seems to be acked by Wei and Reviewed by Dario => applied, thanks
everyone.

> *Its my "bite size contribution" that is required for applying to the
> Outreachy program.
> 
> *main_foo() is treated somewhat as a regular main(), it is changed to
> return EXIT_SUCCESS or EXIT_FAILURE.
> 
> *Functions that are not main_foo(), are changed to do 'return 0' or
> 'return 1', and then 0/1 is taken care in the main_foo() functions
> that calls them.
> 
> *Functions in xl.c and xl_cmdimpl.c are changed.
> 
> *Functions related to scheduling, vcpu, cpupool and parsing are
> currently changed excluding parse_config_data() which is big enough
> to deserve its own patch.
> 
> *Some discussions about this patch:
> https://www.mail-archive.com/xen-devel@lists.xen.org/msg42850.html
> 
> *v1 of this patch:
> http://lists.xenproject.org/archives/html/xen-devel/2015-10/msg02497.html
> 
> *v2 of this patch:
> http://lists.xenproject.org/archives/html/xen-devel/2015-10/msg02623.html
> 
> *v3 of this patch:
> http://lists.xenproject.org/archives/html/xen-devel/2015-10/msg02872.html
> 
> *v4 of this patch:
> http://lists.xenproject.org/archives/html/xen-devel/2015-10/msg02947.html
> 
> *v5 of this patch:
> http://lists.xenproject.org/archives/html/xen-devel/2015-10/msg02990.html
> 
> Signed-off-by: Harmandeep Kaur <write.harmandeep@gmail.com>
> ---

  parent reply	other threads:[~2015-11-04  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  2:26 [PATCH v6 0/5] xl: convert exit codes to EXIT_[SUCCESS|FAILURE] Harmandeep Kaur
2015-10-28  2:26 ` [PATCH v6 1/5] xl: convert main() " Harmandeep Kaur
2015-10-28  2:26 ` [PATCH v6 2/5] xl: improve return and exit codes of scheduling related functions Harmandeep Kaur
2015-10-28  2:26 ` [PATCH v6 3/5] xl: improve return and exit codes of vcpu " Harmandeep Kaur
2015-10-28  2:26 ` [PATCH v6 4/5] xl: improve return and exit codes of parse " Harmandeep Kaur
2015-10-28  2:26 ` [PATCH v6 5/5] " Harmandeep Kaur
2015-11-04  9:40 ` Ian Campbell [this message]
2015-11-04  9:50   ` [PATCH v6 0/5] xl: convert exit codes to EXIT_[SUCCESS|FAILURE] Ian Campbell

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=1446630018.16178.69.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@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).