All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Lasya Venneti <comethalley61@gmail.com>,
	xen-devel@lists.xenproject.org, george.dunlap@citrix.com,
	ian.campbell@citrix.com, wei.liu2@citrix.com,
	stefano.stebellini@eu.citrix.com, lars.kurth@citrix.com
Subject: Re: [PATCH] Fixing coverity bug CID1311511
Date: Mon, 26 Oct 2015 10:09:15 +0100	[thread overview]
Message-ID: <1445850555.2717.8.camel@citrix.com> (raw)
In-Reply-To: <1445767344-7780-1-git-send-email-comethalley61@gmail.com>


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

On Sun, 2015-10-25 at 15:32 +0530, Lasya Venneti wrote:
> *This is part of my 'bite sized contribution' to Xen for the
> OutreachY program. 
> 
> *The change handles the return value of the function xc_dom_allocate,
> if the function returns NULL the function returns -1. It would not be
> useful to jump to err as err would check !dom for NULL. 
> 
But then you're not closing xs_fd, is that ok? (I'm asking, because I
am not at all a xenstore expert, but, FWIW, it does not feel right to
me).

> *Changes have been made in the build function in init-xenstore
> -domain.c
> 
> *I have taken these discussions for reference:
> https://www.choon.net/forum/read.php?22,3805351,3805351
> 
> Signed-off: Lasya Venneti <comethalley61@gmail.com>
>
Most of this (except the first bullet point, perhaps), and especially
the Signed-off-by (it's 'Signed-off-by:', not 'Signed-off') tag goes in
the patch changelog.

In fact:
 - this looks like a cover letter for a patch series, but there is 
   only one patch in this case. Usually, when there is only one patch, 
   you don't need a cover letter (there are exceptions, but I don't 
   think this qualifies);
 - cover letters, no matter whether for series or single patches, do 
   not become part of the source tree, when the patch (series) is 
   committed. That is why, information about the patch 
   content/design/etc. and the tags must live in the changelog. If you 
   do like this, someone looking at `git log' wouldn't see it.

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

  parent reply	other threads:[~2015-10-26  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-25 10:02 [PATCH] Fixing coverity bug CID1311511 Lasya Venneti
2015-10-25 10:02 ` [PATCH] Handles the error returned by the xc_dom_allocate function Lasya Venneti
2015-10-26 10:40   ` Wei Liu
2015-11-02 12:02     ` Ian Campbell
2015-10-26  9:09 ` Dario Faggioli [this message]
2015-10-26  9:18   ` [PATCH] Fixing coverity bug CID1311511 Lasya Venneti
2015-10-26  9:21     ` Lasya Venneti

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=1445850555.2717.8.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=comethalley61@gmail.com \
    --cc=george.dunlap@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=lars.kurth@citrix.com \
    --cc=stefano.stebellini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.