From: Andrew Morton <akpm@linux-foundation.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2 patches for review
Date: Tue, 7 Apr 2015 14:54:53 -0700 [thread overview]
Message-ID: <20150407145453.db5c18c6214fbfbb24537dbd@linux-foundation.org> (raw)
Nine patches for which I feel additional review/test/etc is needed,
please.
Some of these are somewhat old - if people think I should just drop
them then please say so.
ocfs2-trusted-xattr-missing-cap_sys_admin-check.patch
- breaks userspace?
ocfs2-flush-inode-data-to-disk-and-free-inode-when-i_count-becomes-zero.patch
add-errors=continue.patch
acknowledge-return-value-of-ocfs2_error.patch
clear-the-rest-of-the-buffers-on-error.patch
ocfs2-fix-a-tiny-case-that-inode-can-not-removed.patch
ocfs2-use-64bit-variables-to-track-heartbeat-time.patch
ocfs2-call-ocfs2_journal_access_di-before-ocfs2_journal_dirty-in-ocfs2_write_end_nolock.patch
- Mark wants changes. Mark has list of notes
ocfs2-avoid-access-invalid-address-when-read-o2dlm-debug-messages.patch
- Mark has issues
next reply other threads:[~2015-04-07 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 21:54 Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-09 20:03 [Ocfs2-devel] ocfs2 patches for review Andrew Morton
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=20150407145453.db5c18c6214fbfbb24537dbd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ocfs2-devel@oss.oracle.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