From: Dave Chinner <david@fromorbit.com>
To: Dhruvesh Rathore <adrscube@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/4] xfs: xfs_spaceman utility rework
Date: Wed, 11 Feb 2015 11:28:40 +1100 [thread overview]
Message-ID: <20150211002840.GR4251@dastard> (raw)
In-Reply-To: <54ca326a.a1c4440a.6b39.422e@mx.google.com>
On Thu, Jan 29, 2015 at 06:45:17PM +0530, Dhruvesh Rathore wrote:
>
> The original kernel patch that Dave wrote for xfs_spaceman implemented
> FS_IOC_FIEMAPFS ioctl, here is the original fiemap extension patch:
>
> http://oss.sgi.com/archives/xfs/2012-10/msg00363.html
>
> These patches were not posted and were just forward ported to a current
> 3.18-rc7+ for-next XFS tree and were pushed to the fiemapfs branch in Dave's
> kernel tree at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git
>
>
> The original xfs_spaceman tool that Dave wrote to call the fiemap
> interface and make use of it is here:
>
> http://oss.sgi.com/archives/xfs/2012-10/msg00366.html
>
> Dave just updated it to the 3.2.2 code base and pushed it to the
> spaceman branch in this tree:
>
> git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
These tree branches have just been updated (via rebase) with all the
changes in these patches integrated. Please update your trees and
review and test the updated patches. The patches have been
reshuffled and reworked, so please make sure you are happy with the
attributions in the commit messages for the new patches.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-02-11 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 13:15 [PATCH 0/4] xfs: xfs_spaceman utility rework Dhruvesh Rathore
2015-02-11 0:28 ` Dave Chinner [this message]
2015-02-11 16:09 ` Dhruvesh Rathore
-- strict thread matches above, loose matches on Subject: below --
2015-01-28 14:32 Dhruvesh Rathore
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=20150211002840.GR4251@dastard \
--to=david@fromorbit.com \
--cc=adrscube@gmail.com \
--cc=xfs@oss.sgi.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