From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2 patch review for 3.19
Date: Thu, 5 Feb 2015 08:43:47 +0800 [thread overview]
Message-ID: <54D2BCC3.8070109@huawei.com> (raw)
In-Reply-To: <20150204160024.3bfdfa2ecc067c1760f5fdd2@linux-foundation.org>
Hi Andrew,
On 2015/2/5 8:00, Andrew Morton wrote:
>
> Thsi time I have only four patches which I consider need expert review,
> please.
>
> ocfs2-prune-the-dcache-before-deleting-the-dentry-of-directory.patch
>
> o2dlm-fix-null-pointer-dereference-in-o2dlm_blocking_ast_wrapper.patch
> (Joseph Qi had issues)
Srini has already explained the difference with the old version.
I have no issue with this patch now:)
Joseph
>
> ocfs2-call-ocfs2_journal_access_di-before-ocfs2_journal_dirty-in-ocfs2_write_end_nolock.patch
> (Mark has list of things which need doing)
>
> ocfs2-avoid-access-invalid-address-when-read-o2dlm-debug-messages.patch
> (Mark has issues with it)
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>
>
next prev parent reply other threads:[~2015-02-05 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 0:00 [Ocfs2-devel] ocfs2 patch review for 3.19 Andrew Morton
2015-02-05 0:43 ` Joseph Qi [this message]
2015-02-05 22:13 ` Mark Fasheh
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=54D2BCC3.8070109@huawei.com \
--to=joseph.qi@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).