From: Jan Kara <jack@suse.cz>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Jan Kara <jack@suse.cz>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/7] quota: Allow quota support without quota files
Date: Wed, 6 Nov 2019 10:59:11 +0100 [thread overview]
Message-ID: <20191106095911.GB16085@quack2.suse.cz> (raw)
In-Reply-To: <20191106081752.6dhmivu2e4qnkb5d@pengutronix.de>
On Wed 06-11-19 09:17:52, Sascha Hauer wrote:
> Hi Jan,
>
> On Mon, Nov 04, 2019 at 11:51:48AM +0100, Jan Kara wrote:
> > Hello,
> >
> > this patch series refactors quota enabling / disabling code and allows
> > filesystems to implement quota support without providing quota files (ubifs
> > wants to do this).
> >
> > Patches have passed testing with fstests, review is welcome.
>
> Thank you for creating this series. I can confirm my UBIFS quota patches
> are working fine on top of this series. I'll send an updated UBIFS quota
> series shortly.
Thanks for testing! I've pushed the series to linux-next so that it gets
wider exposure and will send it to Linus in the next maintenance window.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2019-11-06 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 10:51 [PATCH 0/7] quota: Allow quota support without quota files Jan Kara
2019-11-04 10:51 ` [PATCH 1/7] quota: Factor out setup of quota inode Jan Kara
2019-11-04 10:51 ` [PATCH 2/7] quota: Simplify dquot_resume() Jan Kara
2019-11-04 10:51 ` [PATCH 3/7] quota: Rename vfs_load_quota_inode() to dquot_load_quota_inode() Jan Kara
2019-11-04 10:51 ` [PATCH 4/7] fs: Use dquot_load_quota_inode() from filesystems Jan Kara
2019-11-04 10:51 ` [PATCH 5/7] quota: Drop dquot_enable() Jan Kara
2019-11-04 10:51 ` [PATCH 6/7] quota: Make dquot_disable() work without quota inodes Jan Kara
2019-11-04 10:51 ` [PATCH 7/7] quota: Handle quotas without quota inodes in dquot_get_state() Jan Kara
2019-11-06 8:17 ` [PATCH 0/7] quota: Allow quota support without quota files Sascha Hauer
2019-11-06 9:59 ` Jan Kara [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=20191106095911.GB16085@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=s.hauer@pengutronix.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;
as well as URLs for NNTP newsgroup(s).