linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: tytso@mit.edu, Namjae Jeon <namjae.jeon@samsung.com>,
	bfoster@redhat.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 v9 4/11] xfsprogs: xfs_io: add finsert command for insert range
Date: Fri, 6 Feb 2015 14:11:29 +1100	[thread overview]
Message-ID: <20150206031129.GL12722@dastard> (raw)
In-Reply-To: <20150205234033.GW4251@dastard>

Hi Namjae,

On Fri, Feb 06, 2015 at 10:40:33AM +1100, Dave Chinner wrote:
> On Thu, Jan 22, 2015 at 12:11:59AM +0900, Namjae Jeon wrote:
> > From: Namjae Jeon <namjae.jeon@samsung.com>
> > 
> > Add finsert command for fallocate FALLOC_FL_INSERT_RANGE flag.
> > 
> > Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> > Signed-off-by: Ashish Sangwan <a.sangwan@samsung.com>
> > Reviewed-by: Brian Foster <bfoster@redhat.com>
> 
> I've just pulled this patch into xfsprogs in preparation for getting
> this functionality fully reviewed and merged in the 3.21 kernel
> cycle.

xfs/293 3s ... - output mismatch (see /home/dave/src/xfstests-dev/results//xfs/293.out.bad)
    --- tests/xfs/293.out       2014-01-20 16:57:34.000000000 +1100
    +++ /home/dave/src/xfstests-dev/results//xfs/293.out.bad    2015-02-06 12:21:47.000000000 +1100
    @@ -1,2 +1,3 @@
     QA output created by 293
     Silence is golden
    +finsert not documented in the xfs_io manpage
    .....

Can you send a patch that updates the xfs_io man page, please?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2015-02-06  3:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 15:11 [PATCH v9 0/11] fs: Introduce FALLOC_FL_INSERT_RANGE for fallocate Namjae Jeon
2015-01-21 15:11 ` [PATCH v9 1/11] fs: Add support " Namjae Jeon
2015-01-21 15:11 ` [PATCH v9 2/11] xfs: " Namjae Jeon
2015-01-21 15:11 ` [PATCH v9 3/11] ext4: " Namjae Jeon
2015-01-21 15:11 ` [PATCH v9 4/11] xfsprogs: xfs_io: add finsert command for insert range Namjae Jeon
2015-02-05 23:40   ` Dave Chinner
2015-02-06  3:11     ` Dave Chinner [this message]
2015-02-06  4:27       ` Namjae Jeon
2015-01-21 15:12 ` [PATCH v9 5/11] xfstests: generic/039: Standard insert range tests Namjae Jeon
2015-01-21 15:12 ` [PATCH v9 6/11] xfstests: generic/040: Delayed allocation insert range Namjae Jeon
2015-01-21 15:12 ` [PATCH v9 7/11] xfstests: generic/041: Multi insert range tests Namjae Jeon
2015-01-21 15:12 ` [PATCH v9 8/11] xfstests: generic/042: Delayed allocation multi insert Namjae Jeon
2015-01-21 15:12 ` [PATCH v9 9/11] xfstests: generic/043: Test multiple fallocate insert/collapse range calls Namjae Jeon
2015-01-21 15:12 ` [PATCH v9 10/11] xfstests: fsstress: Add fallocate insert range operation Namjae Jeon
2015-01-21 15:12 ` [PATCH v9 11/11] xfstests: fsx: " Namjae Jeon
2015-01-22  8:16 ` [PATCH v9 0/11] fs: Introduce FALLOC_FL_INSERT_RANGE for fallocate Michael Kerrisk
2015-01-22  8:52   ` Namjae Jeon

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=20150206031129.GL12722@dastard \
    --to=david@fromorbit.com \
    --cc=a.sangwan@samsung.com \
    --cc=bfoster@redhat.com \
    --cc=linkinjeon@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=tytso@mit.edu \
    --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;
as well as URLs for NNTP newsgroup(s).