From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: majianpeng <majianpeng@gmail.com>,
linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] f2fs:avoid creaing multi debugfs when mount more disks.
Date: Tue, 15 Jan 2013 21:10:27 +0900 [thread overview]
Message-ID: <1358251827.8234.67.camel@kjgkr> (raw)
In-Reply-To: <CAKYAXd9FzxLjYubAbiGKDVVA+mBZ7-5TjtoX0FbvU3fcYx_JPg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
2013-01-15 (화), 20:50 +0900, Namjae Jeon:
> 2013/1/15, Jaegeuk Kim <jaegeuk.kim@samsung.com>:
> > [snip]
> >
> >> void f2fs_destroy_stats(struct f2fs_sb_info *sbi)
> >> {
> >> struct f2fs_stat_info *si = sbi->stat_info;
> >> @@ -354,7 +339,15 @@ void f2fs_destroy_stats(struct f2fs_sb_info *sbi)
> >> kfree(sbi->stat_info);
> >> }
> >>
> >> -void destroy_root_stats(void)
> >> +void __init f2fs_create_root_stats(void)
> >
> > We don't need to add __init here, right?
> As you know, the function f2fs_create_root_stats will only be needed
> at the init time of F2FS filesystem. So, there is no harm making this
> function part of __init section, as this function will never be called
> again.
Oh, I meant it for code consistency at this moment.
No other functions declare that though.
Do we need to write another patch to add __init globally?
> Thanks.
> > Anyway, this patch looks much better to me.
> >
> > Jianpeng, how do you think about this?
> >
> > --
> > Jaegeuk Kim
> > Samsung
> >
--
Jaegeuk Kim
Samsung
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-15 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201301141929076532360@gmail.com>
2013-01-15 7:08 ` [PATCH] f2fs:avoid creaing multi debugfs when mount more disks Jaegeuk Kim
2013-01-15 10:58 ` Namjae Jeon
2013-01-15 11:29 ` Jaegeuk Kim
2013-01-15 11:50 ` Namjae Jeon
2013-01-15 12:10 ` Jaegeuk Kim [this message]
2013-01-15 22:52 ` Namjae Jeon
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=1358251827.8234.67.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=linkinjeon@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=majianpeng@gmail.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).