On 10/04/2015 02:57 AM, Richard Weinberger wrote:
Hi!
Am 15.09.2015 um 11:01 schrieb Dongsheng Yang:
Hi all,
This is the V3 to add quota in ubifs.
Hi Al,
There are some patches about vfs, and
some of them are already Reviewed-by Jan, please
take a look at them. Thanx.
Hi Jan,
There are some new patches for dquot,
please take a look.
Hi Artem and Richard,
please help to review the ubifs part.
Yang, from the discussion with Jan it seems as you'll send an v4 of your
patches.
Shall I wait with reviewing UBIFS specific parts or won't they change in v4?
Please wait for V4, there would be something different. :)
Dongsheng Yang (39):
fs: introduce a ->s_cdev field into struct super_block
fs: cleanup: remove the blank line before EXPORT_SYMBOL
This patch is unrelated to this series. Not sure if it makes sense to
carry it here.
fs: super: cleanup: make the comment of each function aligned
The two commits is about cleanup, but there would be a conflict with
other commits in this thread. So I put them here.
fs: super: consolidate the get_super class functions
fs: super: introduce a get_super_cdev to get super by a cdev reference
fs: super: introduce a get_super_cdev_thawed to get sb by cdev
reference
fs: char_dev: introduce cd_acquire function to acquire cdev
fs: introduce a __lookup_dev for internal using
fs: char_dev: introduce lookup_cdev to get cdev by pathname
fs: dquot: skip invalidate_bdev if bdev is NULL
fs: quota: replace opened calling of ->sync_fs with sync_filesystem
fs: quota: make quota support fs which is running on char dev
fs: introduce a get_qsize() to inode_operations
fs: quota: restore i_flags of quota files in dquot_disable
fs: quota: introduce a callback of restore_iflags to quotactl_ops
Jan, Al, will you take the VFS/quota specific changes or shall I
take them? Of course iff you ACK them.
I think it's better to go through ubifs tree with other commits, but
yes, we need ACKs at first.
Thanx
Yang
Thanks,
//richard
.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
