From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 05/16] vfs: Use lowercase names of quota functions
Date: Wed, 28 Jan 2009 12:19:15 -0500 [thread overview]
Message-ID: <20090128171915.GA11117@infradead.org> (raw)
In-Reply-To: <20090127173540.GF8289@duck.suse.cz>
On Tue, Jan 27, 2009 at 06:35:40PM +0100, Jan Kara wrote:
> On Tue 27-01-09 12:13:23, Christoph Hellwig wrote:
> > On Tue, Jan 27, 2009 at 05:48:38PM +0100, Jan Kara wrote:
> > > Use lowercase names of quota functions instead of old uppercase ones.
> >
> > Looking over this again I think the vfs_ names are a really bad choice.
> > The normal use for vfs_ are higher level functions that call into
> > specific filesystems, which these aren't really. What about just
> > striping out that vfs_ prefix first?
> Actually, these vfs_dq_ functions are usually just wrappers like:
>
> static inline void vfs_dq_init(struct inode *inode)
> {
> BUG_ON(!inode->i_sb);
> if (sb_any_quota_active(inode->i_sb) && !IS_NOQUOTA(inode))
> inode->i_sb->dq_op->initialize(inode, -1);
> }
>
> where ->initialize either leads to a filesystem specified callback or to
> generic quota init function. So this seems to reasonably match your
> description above...
> But if this still has not convinced you ;), I can change all these quota
> functions to have names starting with dq_. That should not clash with
> anything else. But I'm not very enthusiastic about this change (cleanups are
> so boring...).
Hmm, seems you're right - I must have been confused when looking at it.
Changing away from the weird uppercase names defintively is a good
thing.
Although for the ops inside the filesystem it might be better to just
call into the lowlevel operation instead of the vfs_ helper as we know
what we want, no?
next prev parent reply other threads:[~2009-01-28 17:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 16:48 [PATCH 00/16] Quota cleanups Jan Kara
2009-01-27 16:48 ` [PATCH 01/16] quota: Move quota files into separate directory Jan Kara
2009-01-27 16:48 ` [PATCH 02/16] quota: Make global quota locks cacheline aligned Jan Kara
2009-01-27 16:48 ` [PATCH 03/16] quota: Remove NODQUOT macro Jan Kara
2009-01-27 16:48 ` [PATCH 04/16] quota: Remove dqbuf_t and other cleanups Jan Kara
2009-01-27 16:48 ` [PATCH 05/16] vfs: Use lowercase names of quota functions Jan Kara
2009-01-27 16:48 ` [PATCH 06/16] ramfs: Remove quota call Jan Kara
2009-01-27 16:48 ` [PATCH 07/16] ext2: Use lowercase names of quota functions Jan Kara
2009-01-27 16:48 ` [PATCH 08/16] ext3: " Jan Kara
2009-01-27 16:48 ` [PATCH 09/16] ext4: " Jan Kara
2009-01-27 16:48 ` [PATCH 10/16] reiserfs: " Jan Kara
2009-01-27 16:48 ` [PATCH 11/16] ufs: " Jan Kara
2009-01-27 16:48 ` [PATCH 12/16] udf: " Jan Kara
2009-01-27 16:48 ` [PATCH 13/16] jfs: " Jan Kara
2009-01-27 16:48 ` [PATCH 14/16] quota: Remove uppercase aliases for " Jan Kara
2009-01-27 16:48 ` [PATCH 15/16] quota: Remove superfluous inlines Jan Kara
2009-01-27 16:48 ` [PATCH 16/16] quota: Coding style fixes Jan Kara
2009-01-28 23:46 ` [PATCH 13/16] jfs: Use lowercase names of quota functions Dave Kleikamp
2009-01-28 0:13 ` [PATCH 09/16] ext4: " Mingming Cao
2009-01-27 17:13 ` [PATCH 05/16] vfs: " Christoph Hellwig
2009-01-27 17:35 ` Jan Kara
2009-01-28 17:19 ` Christoph Hellwig [this message]
2009-01-28 23:09 ` 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=20090128171915.GA11117@infradead.org \
--to=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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).