From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>, Miklos Szeredi <miklos@szeredi.hu>,
Jan Kara <jack@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [GIT PULL] ext4 changes for 3.15
Date: Tue, 8 Apr 2014 20:47:38 +1000 [thread overview]
Message-ID: <20140408104738.GD22917@dastard> (raw)
In-Reply-To: <20140404202323.GB10275@thunk.org>
On Fri, Apr 04, 2014 at 04:23:23PM -0400, Theodore Ts'o wrote:
> Ah yes, I had forgotten that you had sent those patches, thanks.
>
> It looks like that since you worded it as "just RFC for now since they
> aren't in 3.15 yet", the xfstests folks never actually accepted your
> changes into xfstests, and so I never picked it up.
>
> For future reference, the tests for COLLAPSE_RANGE and ZERO_RANGE were
> accepted into xfstests well before the merge window opened, and that
> was awfully convenience since we could pull the latest from the
> xfstests.git tree and do automated testing while those patches were in
> the ext4 and xfs trees.
The xfstests for those features were merged into xfstests at the
same time the the kernel code was pulled into the XFS tree. i.e.
once the kernel code had been merged into a maintainer's tree. That's
why they were there for the testing you needed to do with ext4.
There hasn't been any XFS patches written for renameat2 and the
patches that were posted as "here's some tests, maybe we'll get
renameat2 into 3.15" so there hasn't been any urgency indicated to
the xfstests folks that they were needed. We've been pretty much out
of the loop here....
> So feel free to be a bit more insistent about asking for your xfstests
> to be merged upstream; you don't have to wait until the changes reach
> mainline.
Actually, we don't add tests to xfstests until the patches that they
test are committed to an upstream repository somewhere. i.e. we need
some guarantee that the code is actually accepted by a maintainer
and is on it's way to mainline before we'll include the tests. We
don't want to have to waste time on reviewing and committing tests
for functionality that never goes into the mainline tree....
> If it's clear that the patches are going to be accepted,
> and they are in the subsystem trees, that's a fine time to push to get
> the changes into xfstests.
I asked whether this patchset is going to make 3.15 and reviewed the
xfstests patches that had been posted earlier today. About 12 hours
before I read this thread.... ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-04-08 10:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 19:15 [GIT PULL] ext4 changes for 3.15 Theodore Ts'o
2014-04-03 19:39 ` Linus Torvalds
2014-04-04 3:53 ` Theodore Ts'o
2014-04-04 13:44 ` Jan Kara
2014-04-04 17:16 ` Miklos Szeredi
2014-04-04 20:23 ` Theodore Ts'o
2014-04-08 10:47 ` Dave Chinner [this message]
2014-04-04 23:43 ` Theodore Ts'o
2014-04-07 13:15 ` Miklos Szeredi
2014-04-07 14:07 ` Theodore Ts'o
2014-04-07 20:25 ` Geert Uytterhoeven
2014-04-08 11:25 ` Heiko Carstens
2014-04-08 16:25 ` Linus Torvalds
2014-04-08 13:47 ` Theodore Ts'o
2014-04-09 16:40 ` Geert Uytterhoeven
2014-04-09 16:55 ` H. Peter Anvin
2014-04-09 17:48 ` Geert Uytterhoeven
2014-04-09 18:23 ` Theodore Ts'o
2014-04-09 19:19 ` H. Peter Anvin
2014-06-24 22:03 ` Maciej W. Rozycki
2014-06-24 22:39 ` Thavatchai Makphaibulchoke
2014-06-24 23:25 ` Maciej W. Rozycki
2014-06-25 17:08 ` Linus Torvalds
2014-06-25 22:37 ` Theodore Ts'o
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=20140408104738.GD22917@dastard \
--to=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).