From: Dave Chinner <david@fromorbit.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs: fix wrong seq order in group file
Date: Mon, 18 Jul 2016 09:31:36 +1000 [thread overview]
Message-ID: <20160717233136.GZ1922@dastard> (raw)
In-Reply-To: <1468558761-22665-1-git-send-email-eguan@redhat.com>
On Fri, Jul 15, 2016 at 12:59:21PM +0800, Eryu Guan wrote:
> 006 and 007 are in reverse order, and this breaks tools to find the
> next available seq number in group file (e.g. tools/nextid).
>
> Signed-off-by: Eryu Guan <eguan@redhat.com>
> ---
> I made this mistake when merging xfs/006, sorry!
>
> tests/xfs/group | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/xfs/group b/tests/xfs/group
> index 9f8ca0f..59d2a85 100644
> --- a/tests/xfs/group
> +++ b/tests/xfs/group
> @@ -3,8 +3,8 @@
> 003 db auto quick
> 004 db auto quick
> 005 auto quick
> -007 auto quota quick
> 006 auto quick mount
> +007 auto quota quick
> 008 rw ioctl auto quick
Reviewed-by: Dave Chinner <dchinner@redhat.com>
-Dave
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-07-17 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 4:59 [PATCH] xfs: fix wrong seq order in group file Eryu Guan
2016-07-17 23:31 ` Dave Chinner [this message]
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=20160717233136.GZ1922@dastard \
--to=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
/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