From: Eryu Guan <eguan@linux.alibaba.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: Eryu Guan <guan@eryu.me>, Christoph Hellwig <hch@lst.de>,
"Darrick J . Wong" <djwong@kernel.org>,
fstests@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v9 0/4 REBASED] fstests: add idmapped mounts tests
Date: Mon, 22 Mar 2021 10:37:04 +0800 [thread overview]
Message-ID: <20210322023704.GC95214@e18g06458.et15sqa> (raw)
In-Reply-To: <20210321153200.t6cgg3sfm4m2aea3@wittgenstein>
On Sun, Mar 21, 2021 at 04:32:00PM +0100, Christian Brauner wrote:
> On Sun, Mar 21, 2021 at 10:26:35PM +0800, Eryu Guan wrote:
> > On Tue, Mar 16, 2021 at 11:36:23AM +0100, Christian Brauner wrote:
> > > Hey everyone,
> > >
> > > /* v9 */
> > > Rebased onto current master.
> > > Hopefully we can merge this soon so we can have regular testing asap and
> > > the rebasing is getting a bit tedious too. ;)
> >
> > Sorry for the late review.. You don't have to rebase on every release if
> > updating the test seq number is the only thing changed. Seq number
> > conflicts all the time, usually I can fix it on commit.
> >
> > Patch 2 is missing from the list, maybe it's too big to post, could you
>
> _Sigh_, this seems like another vger issue. The individual Ccs/Tos
> should've all gotten the patch but it's missing from the list. This is a
> pattern I've seen quite a few times recently with vger. There's nothing
> to do apart from complain about it to the vger maintainer. :)
>
> > please provide a git repo so I can pull from there?
>
> For sure. It's available in three locations:
> https://git.kernel.org/pub/scm/linux/kernel/git/brauner/xfstests-dev.git/log/?h=idmapped_mounts_v2
> https://gitlab.com/brauner/xfstests/-/tree/idmapped_mounts_v2
> https://github.com/brauner/xfstests/tree/idmapped_mounts_v2
Ok, thanks!
>
> (Are you fixing the things you pointed out in the individual patches
> yourself or should I resend a new version?)
New version please, I can fix trival things like typo, renumber the
test, code style, etc.
Thanks,
Eryu
next prev parent reply other threads:[~2021-03-22 2:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 10:36 [PATCH v9 0/4 REBASED] fstests: add idmapped mounts tests Christian Brauner
2021-03-16 10:36 ` [PATCH v9 1/4] generic/631: add test for detached mount propagation Christian Brauner
2021-03-18 6:23 ` Christoph Hellwig
2021-03-18 15:02 ` Darrick J. Wong
2021-03-18 15:14 ` Christian Brauner
2021-03-18 15:57 ` Darrick J. Wong
2021-03-18 16:31 ` Darrick J. Wong
2021-03-21 14:28 ` Eryu Guan
2021-03-22 10:00 ` Christian Brauner
2021-03-16 10:36 ` [PATCH v9 3/4] xfs/529: quotas and idmapped mounts Christian Brauner
2021-03-18 6:24 ` Christoph Hellwig
2021-03-21 14:42 ` Eryu Guan
2021-03-22 10:11 ` Christian Brauner
2021-03-16 10:36 ` [PATCH v9 4/4] xfs/530: quotas on " Christian Brauner
2021-03-18 6:24 ` Christoph Hellwig
2021-03-21 14:51 ` Eryu Guan
2021-03-22 12:25 ` Christian Brauner
[not found] ` <20210316103627.2954121-3-christian.brauner@ubuntu.com>
2021-03-18 6:23 ` [PATCH v9 2/4] generic/632: add fstests for " Christoph Hellwig
2021-03-21 14:26 ` [PATCH v9 0/4 REBASED] fstests: add idmapped mounts tests Eryu Guan
2021-03-21 15:32 ` Christian Brauner
2021-03-22 2:37 ` Eryu Guan [this message]
2021-03-22 9:49 ` Christian Brauner
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=20210322023704.GC95214@e18g06458.et15sqa \
--to=eguan@linux.alibaba.com \
--cc=christian.brauner@ubuntu.com \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=hch@lst.de \
/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