From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Jaegeuk Kim <jaegeuk.kim@samsung.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH 6/6] f2fs: Convert kmem_cache_alloc(...GFP_ZERO) to kmem_cache_zalloc
Date: Thu, 29 Aug 2013 13:11:10 -0700 [thread overview]
Message-ID: <075e5f4b42ddc2d3192a59f8b31e52fd3f220804.1377806578.git.joe@perches.com> (raw)
In-Reply-To: <cover.1377806578.git.joe@perches.com>
The helper exists, might as well use it instead of __GFP_ZERO.
Signed-off-by: Joe Perches <joe@perches.com>
---
fs/f2fs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 13d0a0f..d43709a 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -286,7 +286,7 @@ static struct inode *f2fs_alloc_inode(struct super_block *sb)
{
struct f2fs_inode_info *fi;
- fi = kmem_cache_alloc(f2fs_inode_cachep, GFP_NOFS | __GFP_ZERO);
+ fi = kmem_cache_zalloc(f2fs_inode_cachep, GFP_NOFS);
if (!fi)
return NULL;
--
1.8.1.2.459.gbcd45b4.dirty
prev parent reply other threads:[~2013-08-29 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 20:11 [PATCH 0/6] treewide: kmem_cache_alloc GFP_ZERO cleanups Joe Perches
2013-08-29 20:11 ` [PATCH 1/6] slab/block: Add and use kmem_cache_zalloc_node Joe Perches
2013-08-30 13:37 ` Christoph Lameter
2013-08-29 20:11 ` [PATCH 2/6] block: Convert kmem_cache_alloc(...GFP_ZERO) to kmem_cache_zalloc Joe Perches
2013-08-29 20:11 ` [PATCH 3/6] i915_gem: " Joe Perches
2013-08-29 20:39 ` Daniel Vetter
2013-08-29 20:11 ` [PATCH 4/6] aio: " Joe Perches
2013-08-29 20:11 ` [PATCH 5/6] ceph: " Joe Perches
2013-08-29 20:11 ` Joe Perches [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=075e5f4b42ddc2d3192a59f8b31e52fd3f220804.1377806578.git.joe@perches.com \
--to=joe@perches.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®