ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.de>
To: Gang He <ghe@suse.com>
Cc: rgoldwyn@suse.de, linux-kernel@vger.kernel.org,
	ocfs2-devel@oss.oracle.com, akpm@linux-foundation.org
Subject: [Ocfs2-devel] [PATCH v3 3/4] ocfs2: create/remove sysfile for online file check
Date: Wed, 13 Jan 2016 15:36:21 -0800	[thread overview]
Message-ID: <20160113233621.GM819@wotan.suse.de> (raw)
In-Reply-To: <1451027779-6849-4-git-send-email-ghe@suse.com>

On Fri, Dec 25, 2015 at 03:16:18PM +0800, Gang He wrote:
> Create online file check sysfile when ocfs2 mount,
> remove the related sysfile when ocfs2 umount.
> 
> Signed-off-by: Gang He <ghe@suse.com>

Reviewed-by: Mark Fasheh <mfasheh@suse.de>
	--Mark

--
Mark Fasheh

  reply	other threads:[~2016-01-13 23:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-25  7:16 [Ocfs2-devel] [PATCH v3 0/4] Add online file check feature Gang He
2015-12-25  7:16 ` [Ocfs2-devel] [PATCH v3 1/4] ocfs2: export ocfs2_kset for online file check Gang He
2015-12-29 21:38   ` Andrew Morton
2015-12-30  6:13     ` Gang He
2016-01-13 23:02   ` Mark Fasheh
2016-01-13 23:07     ` Andrew Morton
2015-12-25  7:16 ` [Ocfs2-devel] [PATCH v3 2/4] ocfs2: sysfile interfaces " Gang He
2016-01-13 23:35   ` Mark Fasheh
2016-01-14  3:13     ` Gang He
2015-12-25  7:16 ` [Ocfs2-devel] [PATCH v3 3/4] ocfs2: create/remove sysfile " Gang He
2016-01-13 23:36   ` Mark Fasheh [this message]
2015-12-25  7:16 ` [Ocfs2-devel] [PATCH v3 4/4] ocfs2: check/fix inode block " Gang He
2016-01-14  1:40   ` Mark Fasheh
2016-01-14  6:30     ` Gang He
2015-12-29 21:41 ` [Ocfs2-devel] [PATCH v3 0/4] Add online file check feature Andrew Morton
2015-12-30  3:00   ` Gang He
2015-12-30  3:14     ` 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=20160113233621.GM819@wotan.suse.de \
    --to=mfasheh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ghe@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=rgoldwyn@suse.de \
    /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).