All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: Li Zhong <zhong@linux.vnet.ibm.com>, Eric Sandeen <sandeen@sandeen.net>
Cc: Chandra Seetharaman <sekharan@us.ibm.com>,
	Mark Tinguely <tinguely@sgi.com>, xfsprogs <xfs@oss.sgi.com>
Subject: Re: [PATCH 2/2] xfsprogs: fix return value of verify_set_primary_sb()
Date: Fri, 18 Oct 2013 11:42:57 -0500	[thread overview]
Message-ID: <52616511.3020000@sgi.com> (raw)
In-Reply-To: <1380178092.2983.14.camel@ThinkPad-T5421>

This has been committed.

Thanks
--Rich

commit ae181820d03e19f145dbd058c0f8fa59fa18468c
Author: Li Zhong <zhong@linux.vnet.ibm.com>
Date:   Thu Sep 26 06:48:12 2013 +0000

     xfsprogs: fix return value of verify_set_primary_sb()

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2013-10-18 16:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-22  6:01 [PATCH] xfsprogs: fix potential memory leak in verify_set_primary_sb() Li Zhong
2013-09-24 18:59 ` Mark Tinguely
2013-09-25  7:32   ` [PATCH v2] " Li Zhong
2013-09-25 13:26     ` Mark Tinguely
2013-09-25 14:28     ` Eric Sandeen
2013-09-26  6:41       ` Li Zhong
2013-09-26  6:45       ` [PATCH v3 1/2] " Li Zhong
2013-09-26  6:48         ` [PATCH 2/2] xfsprogs: fix return value of verify_set_primary_sb() Li Zhong
2013-09-26 14:43           ` Eric Sandeen
2013-10-18 16:42           ` Rich Johnston [this message]
2013-09-26 14:31         ` [PATCH v3 1/2] xfsprogs: fix potential memory leak in verify_set_primary_sb() Eric Sandeen
2013-09-27  3:05           ` Li Zhong
2013-09-27  3:24             ` Eric Sandeen
2013-09-27  5:24               ` Li Zhong
2013-10-18 16:40         ` Rich Johnston
2013-09-25  7:34   ` [PATCH] " Li Zhong

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=52616511.3020000@sgi.com \
    --to=rjohnston@sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=sekharan@us.ibm.com \
    --cc=tinguely@sgi.com \
    --cc=xfs@oss.sgi.com \
    --cc=zhong@linux.vnet.ibm.com \
    /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.