linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sunil Mushran <sunil.mushran@oracle.com>
To: akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	ocfs2-devel@oss.oracle.com
Subject: Add FIEMAP_EXTENT_SHARED flag
Date: Thu,  3 Dec 2009 12:46:50 -0800	[thread overview]
Message-ID: <1259873212-20107-1-git-send-email-sunil.mushran@oracle.com> (raw)

Andrew,

Please could you Ack this patch. This adds a new FIEMAP flag to denote
shared extents which we are using to identify such exents in reflinked
files.

Thanks
Sunil

             reply	other threads:[~2009-12-03 20:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 20:46 Sunil Mushran [this message]
2009-12-03 20:46 ` [PATCH 1/2] fiemap: Add new extent flag FIEMAP_EXTENT_SHARED Sunil Mushran
2009-12-03 20:46 ` [PATCH 2/2] ocfs2: Use FIEMAP_EXTENT_SHARED Sunil Mushran
2009-12-18  5:10 ` [Ocfs2-devel] Add FIEMAP_EXTENT_SHARED flag Joel Becker
2009-12-18 21:24   ` Andreas Dilger
2009-12-18 21:30     ` Sunil Mushran

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=1259873212-20107-1-git-send-email-sunil.mushran@oracle.com \
    --to=sunil.mushran@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).