From: Matthew Wilcox <matthew@wil.cx>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel@vger.kernel.org, jack@suse.cz, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/1] ext2: Add __init macro to init_inodecache
Date: Sat, 1 Feb 2014 10:53:34 -0700 [thread overview]
Message-ID: <20140201175334.GJ20939@parisc-linux.org> (raw)
In-Reply-To: <20140201160202.a3ac96c613754013300b462d@skynet.be>
On Sat, Feb 01, 2014 at 04:02:02PM +0800, Fabian Frederick wrote:
> init_inodecache is only called by __init init_ext2_fs.
Looks like this is true for the majority of filesystems. Would you care
to submit more patches? :-)
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2014-02-01 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 8:02 [PATCH 1/1] ext2: Add __init macro to init_inodecache Fabian Frederick
2014-02-01 17:53 ` Matthew Wilcox [this message]
2014-02-01 10:19 ` Fabian Frederick
2014-02-03 23:56 ` Jan Kara
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=20140201175334.GJ20939@parisc-linux.org \
--to=matthew@wil.cx \
--cc=fabf@skynet.be \
--cc=jack@suse.cz \
--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).