From: Edward Shishkin <edward.shishkin@gmail.com>
To: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Reiser4 for Linux-3.7
Date: Sun, 06 Jan 2013 21:42:10 +0100 [thread overview]
Message-ID: <50E9E1A2.4040400@gmail.com> (raw)
Changes since 3.6:
Ivan Shapovalov
. Port for linux-3.7;
. make reiser4 mapping not movable (always fail migration).
Edward Shishkin
. Ifdef reiser4_migratepage to prevent compilation error
in the case when CONFIG_MIGRATION is not defined;
. Use separate foo_bugop() instead of the common bugop()
to understand in what stub the oops occured;
. Don't set zeros to the body of ctail item in debug mode
(where extra-modifications are highly undesirable);
. Use "dispatch" prefix for file operations, which pass
management to FILE plugins in accordance with inode's
plugin table (pset);
. Update comments.
Please, find here:
http://sourceforge.net/projects/reiser4/files/reiser4-for-linux-3.x/
Thanks,
Edward.
reply other threads:[~2013-01-06 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50E9E1A2.4040400@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=reiserfs-devel@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).