From: npiggin@suse.de
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [patch 0/5] initial fs patches
Date: Sun, 26 Apr 2009 20:25:52 +1000 [thread overview]
Message-ID: <20090426102552.947523845@suse.de> (raw)
OK, here are the first few patches again, reordered and with the
suggested fixes.
next reply other threads:[~2009-04-26 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 10:25 npiggin [this message]
2009-04-26 10:25 ` [patch 1/5] fs: dcache fix LRU ordering npiggin
2009-04-26 10:25 ` [patch 2/5] fs: mnt_want_write speedup npiggin
2009-04-26 10:25 ` [patch 3/5] fs: introduce mnt_clone_write npiggin
2009-04-26 10:25 ` [patch 4/5] fs: move mark_files_ro into file_table.c npiggin
2009-04-26 10:25 ` [patch 5/5] fs: cleanup files_lock npiggin
2009-04-26 22:37 ` James Morris
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=20090426102552.947523845@suse.de \
--to=npiggin@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).