From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: fix for lazy-sb
Date: Wed, 2 Dec 2009 10:05:17 -0500 [thread overview]
Message-ID: <20091202150517.GB16338@infradead.org> (raw)
In-Reply-To: <4B156ED2.9000209@sandeen.net>
On Tue, Dec 01, 2009 at 01:30:26PM -0600, Eric Sandeen wrote:
> Fix tests which would be affected by a change to lazy-sb
> by default.
>
> All tests now explicitly -specify- -l lazy-sb=1 where appropriate,
> so this can go in prior to a userspace change.
>
> Unfortunately many of the logprint outputs must just be taken on faith.
>
> Also, the irix flavors for e.g. 018.op.irix will need fixing up
> if anyone cares.
>
> This also needs the patch I just sent for xfs_db clearing attr2
> in bad_features2 to complete w/o error.
>
> Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Looks good to me,
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-12-02 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 19:30 [PATCH] xfstests: fix for lazy-sb Eric Sandeen
2009-12-02 15:05 ` Christoph Hellwig [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=20091202150517.GB16338@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@sandeen.net \
--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