From: Jan Kara <jack@suse.cz>
To: Zheng Liu <gnehzuil.liu@gmail.com>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>,
Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [PATCH] jbd: use kmem_cache_zalloc instead of kmem_cache_alloc/memset
Date: Thu, 25 Apr 2013 15:27:08 +0200 [thread overview]
Message-ID: <20130425132708.GB32353@quack.suse.cz> (raw)
In-Reply-To: <20130425101249.GA16770@gmail.com>
On Thu 25-04-13 18:12:49, Zheng Liu wrote:
> On Fri, Apr 12, 2013 at 08:24:06PM +0800, Zheng Liu wrote:
> > From: Zheng Liu <wenqing.lz@taobao.com>
> >
> > Now jbd_alloc_handle is only called by new_handle. So this commit
> > uses kmem_cache_zalloc instead of kmem_cache_alloc/memset.
> >
> > Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
>
> Hi Jan,
>
> Sorry, I forgot to Cc you. Could you please take a look at this patch?
Yeah, I must have missed it somehow. The patch looks fine, thanks. I've
added it to my tree.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2013-04-25 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 12:24 [PATCH] jbd: use kmem_cache_zalloc instead of kmem_cache_alloc/memset Zheng Liu
2013-04-25 10:12 ` Zheng Liu
2013-04-25 13:27 ` Jan Kara [this message]
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=20130425132708.GB32353@quack.suse.cz \
--to=jack@suse.cz \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@taobao.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