From: Jan Schmidt <mail@jan-o-sch.net>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>,
Jan Schmidt <list.btrfs@jan-o-sch.net>,
xfs@oss.sgi.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] xfstests: new check 278 to ensure btrfs backref integrity
Date: Wed, 04 Jan 2012 18:04:51 +0100 [thread overview]
Message-ID: <4F0486B3.8010301@jan-o-sch.net> (raw)
In-Reply-To: <4F0485FE.8000405@sandeen.net>
On 04.01.2012 18:01, Eric Sandeen wrote:
> 276 got merged on Dec 28 before my requests for fixup, I guess? And it
> explicitly sets FSTYP=btrfs which is why it fails.
>
> the 278 patch v2 in this thread works ok for me.
>
> so munging the 278 patch here into the existing 276 should be the
> right approach.
Yeah we figured that out on irc some minutes ago :-)
I'm currently building v2 as an incremental patch to 276 (without rename
to 278) and send it as
[PATCH] xfstests: fixup check 276
soon.
-Jan
WARNING: multiple messages have this Message-ID (diff)
From: Jan Schmidt <mail@jan-o-sch.net>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-btrfs@vger.kernel.org,
Jan Schmidt <list.btrfs@jan-o-sch.net>,
xfs@oss.sgi.com
Subject: Re: [PATCH v2] xfstests: new check 278 to ensure btrfs backref integrity
Date: Wed, 04 Jan 2012 18:04:51 +0100 [thread overview]
Message-ID: <4F0486B3.8010301@jan-o-sch.net> (raw)
In-Reply-To: <4F0485FE.8000405@sandeen.net>
On 04.01.2012 18:01, Eric Sandeen wrote:
> 276 got merged on Dec 28 before my requests for fixup, I guess? And it
> explicitly sets FSTYP=btrfs which is why it fails.
>
> the 278 patch v2 in this thread works ok for me.
>
> so munging the 278 patch here into the existing 276 should be the
> right approach.
Yeah we figured that out on irc some minutes ago :-)
I'm currently building v2 as an incremental patch to 276 (without rename
to 278) and send it as
[PATCH] xfstests: fixup check 276
soon.
-Jan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-04 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 11:08 [PATCH v2] xfstests: new check 278 to ensure btrfs backref integrity Jan Schmidt
2011-12-22 11:08 ` Jan Schmidt
2012-01-04 16:39 ` Christoph Hellwig
2012-01-04 16:39 ` Christoph Hellwig
2012-01-04 17:01 ` Eric Sandeen
2012-01-04 17:01 ` Eric Sandeen
2012-01-04 17:04 ` Jan Schmidt [this message]
2012-01-04 17:04 ` Jan Schmidt
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=4F0486B3.8010301@jan-o-sch.net \
--to=mail@jan-o-sch.net \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
--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 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.