From: Harmandeep Kaur <write.harmandeep@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org,
Dario Faggioli <dario.faggioli@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v4] libxl: handle failure of xc_version() in libxl_get_version_info()
Date: Wed, 2 Mar 2016 12:51:32 +0530 [thread overview]
Message-ID: <CAPtdW16CNgdUGei1eO2eGCT9PZ_OE0nMybcnipkofHmrCNY6XA@mail.gmail.com> (raw)
In-Reply-To: <22229.40377.351245.228274@mariner.uk.xensource.com>
On Tue, Mar 1, 2016 at 7:18 PM, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> Harmandeep Kaur writes ("[PATCH v4] libxl: handle failure of xc_version() in libxl_get_version_info()"):
>> Check the return value of xc_version() and return NULL if it
>> fails. libxl_get_version_info() can also return NULL now.
>>
>> Callers of the function libxl_get_version_info() are already
>> prepared to deal with a NULL return value.
>
> Thanks for your submission.
>
>> long xen_version;
>> + long r = 0;
>
> Why did you choose `long' for the type of `r' ? Normally it would be
> an int and AFAICT xc_version returns int.
"xen_version" is already using long. Thats the only reason I used long
fot 'r' . We can make int r , no issues there.
>
>> v3: Group all calls to xc_version() , so that data copies in
>> various info fields only if all calls to xc_version work.
>
> This should be in the main part of the commit message, and also the
> explanation of why it is necessary.
>
> Thanks,
> Ian.
Thanks for the help.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-03-02 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 11:07 [PATCH v4] libxl: handle failure of xc_version() in libxl_get_version_info() Harmandeep Kaur
2016-02-24 17:53 ` Dario Faggioli
2016-03-01 13:48 ` Ian Jackson
2016-03-02 7:21 ` Harmandeep Kaur [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=CAPtdW16CNgdUGei1eO2eGCT9PZ_OE0nMybcnipkofHmrCNY6XA@mail.gmail.com \
--to=write.harmandeep@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.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).