From: Theodore Ts'o <tytso@mit.edu>
To: Li Xi <pkuelelixi@gmail.com>
Cc: linux-ext4@vger.kernel.org, adilger@dilger.ca, jack@suse.cz,
viro@zeniv.linux.org.uk, hch@infradead.org, dmonakhov@openvz.org
Subject: Re: [v16 0/4] ext4: add project quota support
Date: Tue, 12 Jan 2016 12:45:56 -0500 [thread overview]
Message-ID: <20160112174556.GA22719@thunk.org> (raw)
In-Reply-To: <1452588970-18309-1-git-send-email-lixi@ddn.com>
Hi Li,
The ext4 project quota patches are in the ext4.git tree and are
planned to be merged during this merge window. I've already made some
changes to fix problems that were reported by zero day testting
service (when CONFIG_QUOTA was not enabled, for example). Since
you've reported that the only changes in this patch series was to
rebase it to the 4.4 kernel, I don't plan to be taking a close look at
this version of the patches; please let me know if there were any
changes beyond just the rebasing changes.
Also, if you could take a look at the project quota patches in the
ext4.git tree, please let me know if you have changes you would like
since this is what I plan to be sending to Linus in the next few days.
Many thanks!
- Ted
next prev parent reply other threads:[~2016-01-12 17:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 8:56 [v16 0/4] ext4: add project quota support Li Xi
2016-01-12 8:56 ` [v16 1/4] ext4: adds project ID support Li Xi
2016-01-12 8:56 ` [v16 2/4] ext4: adds project quota support Li Xi
2016-01-12 9:30 ` kbuild test robot
2016-01-12 11:05 ` kbuild test robot
2016-01-18 0:07 ` kbuild test robot
2016-01-12 8:56 ` [v16 3/4] ext4: adds FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR interface support Li Xi
2016-01-18 0:16 ` kbuild test robot
2016-01-12 8:56 ` [v16 4/4] ext4: cleanup inode flag definitions Li Xi
2016-01-12 17:45 ` Theodore Ts'o [this message]
2016-01-13 1:15 ` [v16 0/4] ext4: add project quota support Li Xi
2016-01-13 3:12 ` Li Xi
2016-01-13 9:52 ` Jan Kara
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=20160112174556.GA22719@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=dmonakhov@openvz.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=pkuelelixi@gmail.com \
--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).