All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
	xen-devel@lists.xenproject.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/xen/grant-table.c: Be sure of unsigned value never comparing with 0
Date: Wed, 27 Aug 2014 18:27:07 +0800	[thread overview]
Message-ID: <53FDB27B.7040001@gmail.com> (raw)
In-Reply-To: <53FDADA5.6070802@citrix.com>

On 8/27/14 18:06, David Vrabel wrote:
> 
> Applied to devel/for-linus-3.18 with this description:
> 
>     xen/grant-table: refactor error cleanup in grow_gnttab_list()
> 
>     The cleanup loop in grow_gnttab_list() is safe from the underflow of
>     the unsigned 'i' since nr_glist_frames is >= 1, but refactor it
>     anyway.
> 

OK, thank you very much for your encouragement! And next, I shall try to
provide another patches for Xen (hope I can finish within this month).
And I should be more careful about the patches which I shall send.

Also I want to consult: "Is there a common test for Xen"? If there is,
please let me know, and I should try to perform the common test before
send any patches.

Welcome any additional ideas, suggestions, and completions.

Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  parent reply	other threads:[~2014-08-27 10:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 15:38 [PATCH] drivers/xen/grant-table.c: Be sure of unsigned value never comparing with 0 Chen Gang
2014-08-26 17:03 ` David Vrabel
2014-08-26 17:03 ` David Vrabel
2014-08-26 19:42   ` Chen Gang
2014-08-26 19:42   ` Chen Gang
2014-08-27 10:06     ` David Vrabel
2014-08-27 10:06     ` David Vrabel
2014-08-27 10:27       ` Chen Gang
2014-08-27 10:27       ` Chen Gang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-26 15:38 Chen Gang

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=53FDB27B.7040001@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.