From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/1] HFSPLUS: add __init to hfsplus_create_attr_tree_cache()
Date: Tue, 11 Mar 2014 10:38:08 +0400 [thread overview]
Message-ID: <1394519888.2191.1.camel@slavad-CELSIUS-H720> (raw)
In-Reply-To: <20140310215658.965a9750989dc3866713afd0@skynet.be>
On Mon, 2014-03-10 at 21:56 +0100, Fabian Frederick wrote:
> hfsplus_create_attr_tree_cache is only called by __init init_hfsplus_fs
>
I think that it is the reasonable fix. Looks good for me.
Reviewed-by: Vyacheslav Dubeyko <slava@dubeyko.com>
Thanks,
Vyacheslav Dubeyko.
> Signed-off-by: Fabian Frederick <fabf@skynet.be>
> ---
> fs/hfsplus/attributes.c | 2 +-
> fs/hfsplus/hfsplus_fs.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/hfsplus/attributes.c b/fs/hfsplus/attributes.c
> index 0f47890..caf89a7 100644
> --- a/fs/hfsplus/attributes.c
> +++ b/fs/hfsplus/attributes.c
> @@ -11,7 +11,7 @@
>
> static struct kmem_cache *hfsplus_attr_tree_cachep;
>
> -int hfsplus_create_attr_tree_cache(void)
> +int __init hfsplus_create_attr_tree_cache(void)
> {
> if (hfsplus_attr_tree_cachep)
> return -EEXIST;
> diff --git a/fs/hfsplus/hfsplus_fs.h b/fs/hfsplus/hfsplus_fs.h
> index 08846425b..bb75586 100644
> --- a/fs/hfsplus/hfsplus_fs.h
> +++ b/fs/hfsplus/hfsplus_fs.h
> @@ -366,7 +366,7 @@ typedef int (*search_strategy_t)(struct hfs_bnode *,
> */
>
> /* attributes.c */
> -int hfsplus_create_attr_tree_cache(void);
> +int __init hfsplus_create_attr_tree_cache(void);
> void hfsplus_destroy_attr_tree_cache(void);
> hfsplus_attr_entry *hfsplus_alloc_attr_entry(void);
> void hfsplus_destroy_attr_entry(hfsplus_attr_entry *entry_p);
prev parent reply other threads:[~2014-03-11 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 20:56 [PATCH 1/1] HFSPLUS: add __init to hfsplus_create_attr_tree_cache() Fabian Frederick
2014-03-11 6:38 ` Vyacheslav Dubeyko [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=1394519888.2191.1.camel@slavad-CELSIUS-H720 \
--to=slava@dubeyko.com \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=linux-fsdevel@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).