From: Rich Johnston <rjohnston@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
elder@kernel.org, tytso@mit.edu,
Namjae Jeon <namjae.jeon@samsung.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com, hch@infradead.org,
bpm@sgi.com, adilger.kernel@dilger.ca, viro@zeniv.linux.org.uk,
a.sangwan@samsung.com, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, mtk.manpages@gmail.com
Subject: Re: [PATCH RESEND 4/7] xfsprogs: xfsio: add support FALLOC_FL_COLLAPSE_RANGE for fallocate
Date: Tue, 22 Oct 2013 10:21:33 -0500 [thread overview]
Message-ID: <526697FD.1090406@sgi.com> (raw)
In-Reply-To: <20131018224404.GX4446@dastard>
This commit was reverted
commit 19e73c9d220728617816c47a1671cc931c40e45b
Author: Rich Johnston <rjohnston@sgi.com>
Date: Tue Oct 22 10:15:20 2013 -0500
Revert "[RESEND, 4/7] xfsprogs: xfsio: add support
FALLOC_FL_COLLAPSE_RANGE for fallocate"
This reverts commit e64190f8440286a815060524777b435e06a7b364 until we
have the fallocate API support merged into the kernel. The kernel
code is still under review.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Rich Johnston <rjohnston@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Namjae Jeon <linkinjeon@gmail.com>, <viro@zeniv.linux.org.uk>,
<mtk.manpages@gmail.com>, <tytso@mit.edu>,
<adilger.kernel@dilger.ca>, <bpm@sgi.com>, <elder@kernel.org>,
<hch@infradead.org>, Namjae Jeon <namjae.jeon@samsung.com>,
<linux-kernel@vger.kernel.org>, <xfs@oss.sgi.com>,
<a.sangwan@samsung.com>, <linux-fsdevel@vger.kernel.org>,
<linux-ext4@vger.kernel.org>
Subject: Re: [PATCH RESEND 4/7] xfsprogs: xfsio: add support FALLOC_FL_COLLAPSE_RANGE for fallocate
Date: Tue, 22 Oct 2013 10:21:33 -0500 [thread overview]
Message-ID: <526697FD.1090406@sgi.com> (raw)
In-Reply-To: <20131018224404.GX4446@dastard>
This commit was reverted
commit 19e73c9d220728617816c47a1671cc931c40e45b
Author: Rich Johnston <rjohnston@sgi.com>
Date: Tue Oct 22 10:15:20 2013 -0500
Revert "[RESEND, 4/7] xfsprogs: xfsio: add support
FALLOC_FL_COLLAPSE_RANGE for fallocate"
This reverts commit e64190f8440286a815060524777b435e06a7b364 until we
have the fallocate API support merged into the kernel. The kernel
code is still under review.
next prev parent reply other threads:[~2013-10-22 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 20:13 [PATCH RESEND 4/7] xfsprogs: xfsio: add support FALLOC_FL_COLLAPSE_RANGE for fallocate Namjae Jeon
2013-10-06 20:13 ` Namjae Jeon
2013-10-09 23:07 ` Dave Chinner
2013-10-09 23:07 ` Dave Chinner
2013-10-18 17:24 ` Rich Johnston
2013-10-18 17:24 ` Rich Johnston
2013-10-18 17:24 ` Rich Johnston
2013-10-18 22:44 ` Dave Chinner
2013-10-18 22:44 ` Dave Chinner
2013-10-18 22:45 ` Rich Johnston
2013-10-18 22:45 ` Rich Johnston
2013-10-22 15:21 ` Rich Johnston [this message]
2013-10-22 15:21 ` Rich Johnston
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=526697FD.1090406@sgi.com \
--to=rjohnston@sgi.com \
--cc=a.sangwan@samsung.com \
--cc=adilger.kernel@dilger.ca \
--cc=bpm@sgi.com \
--cc=david@fromorbit.com \
--cc=elder@kernel.org \
--cc=hch@infradead.org \
--cc=linkinjeon@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=namjae.jeon@samsung.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.