linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
	Seth Jennings <sjenning@linux.vnet.ibm.com>,
	Dan Magenheimer <dan.magenheimer@oracle.com>,
	Konrad Wilk <konrad.wilk@oracle.com>,
	Nitin Gupta <ngupta@vflare.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH v2 1/9] zcache: fix refcount leak
Date: Mon, 9 Jul 2012 07:47:40 -0700	[thread overview]
Message-ID: <20120709144740.GA3961@kroah.com> (raw)
In-Reply-To: <4FFA7266.6090408@linux.vnet.ibm.com>

On Mon, Jul 09, 2012 at 01:55:50PM +0800, Xiao Guangrong wrote:
> On 06/27/2012 01:44 PM, Greg Kroah-Hartman wrote:
> > On Wed, Jun 27, 2012 at 12:47:22PM +0800, Xiao Guangrong wrote:
> >> On 06/27/2012 06:36 AM, Konrad Rzeszutek Wilk wrote:
> >>> On Tue, Jun 26, 2012 at 04:49:46PM +0800, Xiao Guangrong wrote:
> >>>> In zcache_get_pool_by_id, the refcount of zcache_host is not increased, but
> >>>> it is always decreased in zcache_put_pool
> >>>
> >>> All of the patches (1-9) look good to me, so please also
> >>> affix 'Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>'.
> >>>
> >>
> >> Thank you, Konrad!
> >>
> >> Greg, need i repost this patchset with Konrad's Reviewed-by?
> > 
> > No, I can add it when I apply them.
> > 
> 
> 
> Greg, sorry to trouble you but this patches stayed in the list for
> nearly two weeks. If it is ok, could you please apply them? :)

I have now returned from my vacation that I was on for parts of the last
two weeks and am digging out through my patch queue.  I'll get to these
soon, thanks for your patience.

greg k-h

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-07-09 14:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4FE97792.9020807@linux.vnet.ibm.com>
2012-06-26  8:49 ` [PATCH v2 1/9] zcache: fix refcount leak Xiao Guangrong
2012-06-26 22:36   ` Konrad Rzeszutek Wilk
2012-06-27  4:47     ` Xiao Guangrong
2012-06-27  5:44       ` Greg Kroah-Hartman
2012-07-09  5:55         ` Xiao Guangrong
2012-07-09 14:47           ` Greg Kroah-Hartman [this message]
2012-06-26  8:50 ` [PATCH v2 2/9] zcache: fix a compile warning Xiao Guangrong
2012-06-26  8:50 ` [PATCH v2 3/9] zcache: remove unnecessary config option dependence Xiao Guangrong
2012-06-26  8:50 ` [PATCH v2 4/9] zcache: mark zbud_init/zcache_comp_init as __init Xiao Guangrong
2012-06-26  8:51 ` [PATCH v2 5/9] zcache: cleanup zbud_init Xiao Guangrong
2012-06-26  8:51 ` [PATCH v2 6/9] zcache: optimize zcache_do_preload Xiao Guangrong
2012-06-26  8:51 ` [PATCH v2 7/9] zcache: cleanup zcache_do_preload and zcache_put_page Xiao Guangrong
2012-06-26  8:52 ` [PATCH v2 8/9] zcache: introduce get_zcache_client Xiao Guangrong
2012-06-26  8:52 ` [PATCH v2 9/9] zcache: cleanup the code between tmem_obj_init and tmem_obj_find Xiao Guangrong

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=20120709144740.GA3961@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.magenheimer@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@darnok.org \
    --cc=linux-mm@kvack.org \
    --cc=ngupta@vflare.org \
    --cc=sjenning@linux.vnet.ibm.com \
    --cc=xiaoguangrong@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 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).