All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: Re: [patch] staging: lustre: potential underflow in libcfs_kkuc_group_add()
Date: Wed, 04 Nov 2015 18:25:29 +0000	[thread overview]
Message-ID: <20151104182529.GK7289@mwanda> (raw)
In-Reply-To: <563947EC.9020502@cray.com>

On Tue, Nov 03, 2015 at 05:49:00PM -0600, Frank Zago wrote:
> Yes, but for consistency, all 4 functions should be changed.

Thanks for the review.  I will send a v2.

regards,
dan carpenter


WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [patch] staging: lustre: potential underflow in libcfs_kkuc_group_add()
Date: Wed, 4 Nov 2015 21:25:29 +0300	[thread overview]
Message-ID: <20151104182529.GK7289@mwanda> (raw)
In-Reply-To: <563947EC.9020502@cray.com>

On Tue, Nov 03, 2015 at 05:49:00PM -0600, Frank Zago wrote:
> Yes, but for consistency, all 4 functions should be changed.

Thanks for the review.  I will send a v2.

regards,
dan carpenter

  reply	other threads:[~2015-11-04 18:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06  9:57 [patch] staging: lustre: potential underflow in mdc_iocontrol() Dan Carpenter
2015-10-29 13:51 ` [patch] staging: lustre: potential underflow in libcfs_kkuc_group_add() Dan Carpenter
2015-10-29 13:51   ` [lustre-devel] " Dan Carpenter
2015-11-03 23:28   ` Simmons, James A.
2015-11-03 23:28     ` [lustre-devel] " Simmons, James A.
2015-11-03 23:49     ` Frank Zago
2015-11-03 23:49       ` [lustre-devel] " Frank Zago
2015-11-04 18:25       ` Dan Carpenter [this message]
2015-11-04 18:25         ` Dan Carpenter
2015-11-04 19:00         ` Simmons, James A.
2015-11-04 19:00           ` [lustre-devel] " Simmons, James A.

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=20151104182529.GK7289@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=lustre-devel@lists.lustre.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.