Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2 patch review for 3.19
Date: Thu, 5 Feb 2015 14:13:00 -0800	[thread overview]
Message-ID: <20150205221300.GF21790@wotan.suse.de> (raw)
In-Reply-To: <20150204160024.3bfdfa2ecc067c1760f5fdd2@linux-foundation.org>

On Wed, Feb 04, 2015 at 04:00:24PM -0800, 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)

Both reviewed now, thank you Andrew.


> 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)

Unless I'm mistaken, I don't have newer versions of either of these in my inbox
so we should push them off for the next merge window or drop them.

Thanks again,
	--Mark

--
Mark Fasheh

      parent reply	other threads:[~2015-02-05 22:13 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
2015-02-05 22:13 ` Mark Fasheh [this message]

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=20150205221300.GF21790@wotan.suse.de \
    --to=mfasheh@suse.de \
    --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