From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: RFC: merging the quota source files
Date: Tue, 30 Aug 2011 08:11:12 -0400 [thread overview]
Message-ID: <20110830121112.GA19509@infradead.org> (raw)
Hi,
I've started a bit work on the quota code, and the split between the
implementation files is rather annoying. I'd suggest we merge at least
xfs_dquot.c and xfs_qm.c into a single file, as there is no visible
split. Given how small and useless xfs_qm_bhv.c is I'd throw it in.
As a second pass I'd also like to kill xfs_qm_syscalls.c and merge
it into the new xfs_qm.c/xfs_dquot.c for the low-level helpers, and
xfs_quotaops.c for high-level code that deals directly with the Linux
interface.
Does this a) sound good to others, and b) does anyone have a preference
for the name of the new quota implementation file?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-08-30 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 12:11 Christoph Hellwig [this message]
2011-08-31 0:22 ` RFC: merging the quota source files Dave Chinner
2011-08-31 5:20 ` Christoph Hellwig
2011-08-31 12:17 ` Dave Chinner
2011-08-31 12:37 ` Christoph Hellwig
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=20110830121112.GA19509@infradead.org \
--to=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/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