From: Jan Kara <jack@suse.cz>
To: Julia Lawall <julia@diku.dk>
Cc: Jan Kara <jack@suse.cz>,
kernel-janitors@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] fs/ext2/balloc.c: delete useless initialization
Date: Thu, 4 Aug 2011 12:39:54 +0200 [thread overview]
Message-ID: <20110804103954.GG17196@quack.suse.cz> (raw)
In-Reply-To: <1312453774-23333-3-git-send-email-julia@diku.dk>
On Thu 04-08-11 12:29:32, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> Delete nontrivial initialization that is immediately overwritten by the
> result of an allocation function.
Thanks. Merged.
Honza
>
> The semantic match that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> type T;
> identifier i;
> expression e;
> @@
>
> (
> T i = \(0\|NULL\|ERR_PTR(...)\);
> |
> -T i = e;
> +T i;
> )
> ... when != i
> i = \(kzalloc\|kcalloc\|kmalloc\)(...);
>
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
>
> ---
> fs/ext2/balloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -u -p a/fs/ext2/balloc.c b/fs/ext2/balloc.c
> --- a/fs/ext2/balloc.c
> +++ b/fs/ext2/balloc.c
> @@ -421,7 +421,7 @@ static inline int rsv_is_empty(struct ex
> void ext2_init_block_alloc_info(struct inode *inode)
> {
> struct ext2_inode_info *ei = EXT2_I(inode);
> - struct ext2_block_alloc_info *block_i = ei->i_block_alloc_info;
> + struct ext2_block_alloc_info *block_i;
> struct super_block *sb = inode->i_sb;
>
> block_i = kmalloc(sizeof(*block_i), GFP_NOFS);
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2011-08-04 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1312453774-23333-1-git-send-email-julia@diku.dk>
2011-08-04 10:29 ` [PATCH 1/4] fs/ext3/balloc.c: delete useless initialization Julia Lawall
2011-08-04 10:40 ` Jan Kara
2011-08-05 17:24 ` Eric Sandeen
2011-08-05 19:08 ` Julia Lawall
2011-08-04 10:29 ` [PATCH 2/4] fs/ext2/balloc.c: " Julia Lawall
2011-08-04 10:39 ` 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=20110804103954.GG17196@quack.suse.cz \
--to=jack@suse.cz \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).