linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cheng Renquan <crquan@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: [RFC] How about moving&categorizing files under fs/ into separate sub-dirs?
Date: Fri, 8 Jan 2010 11:24:07 +0800	[thread overview]
Message-ID: <91b13c311001071924n19667f65if6551c3c89f29ba3@mail.gmail.com> (raw)

Recently I am working on add a new binfmt support to linux, I think
according current fs/ layout,
it should be placed as fs/binfmt_new.c? but the files under fs/ are
already too many, 70+,
so how about we move and categorize them into different sub-dirs?

like this? I created two sub-dirs, binfmt/ and vfs/, or like net/,
create a net/core/, net/ is relatively clean,
or some other scheme also works, this one is very primitive,

#	renamed:    fs/binfmt_aout.c -> fs/binfmt/binfmt_aout.c
#	renamed:    fs/binfmt_elf.c -> fs/binfmt/binfmt_elf.c
#	renamed:    fs/binfmt_elf_fdpic.c -> fs/binfmt/binfmt_elf_fdpic.c
#	renamed:    fs/binfmt_em86.c -> fs/binfmt/binfmt_em86.c
#	renamed:    fs/binfmt_flat.c -> fs/binfmt/binfmt_flat.c
#	renamed:    fs/binfmt_misc.c -> fs/binfmt/binfmt_misc.c
#	renamed:    fs/binfmt_script.c -> fs/binfmt/binfmt_script.c
#	renamed:    fs/binfmt_som.c -> fs/binfmt/binfmt_som.c
#	renamed:    fs/compat_binfmt_elf.c -> fs/binfmt/compat_binfmt_elf.c
#	renamed:    fs/exec.c -> fs/binfmt/exec.c
#	renamed:    fs/aio.c -> fs/vfs/aio.c
#	renamed:    fs/anon_inodes.c -> fs/vfs/anon_inodes.c
#	renamed:    fs/attr.c -> fs/vfs/attr.c
#	renamed:    fs/bad_inode.c -> fs/vfs/bad_inode.c
#	renamed:    fs/bio-integrity.c -> fs/vfs/bio-integrity.c
#	renamed:    fs/bio.c -> fs/vfs/bio.c
#	renamed:    fs/block_dev.c -> fs/vfs/block_dev.c
#	renamed:    fs/buffer.c -> fs/vfs/buffer.c
#	renamed:    fs/char_dev.c -> fs/vfs/char_dev.c
#	renamed:    fs/dcache.c -> fs/vfs/dcache.c

-- 
Cheng Renquan, from Singapore

                 reply	other threads:[~2010-01-08  3:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=91b13c311001071924n19667f65if6551c3c89f29ba3@mail.gmail.com \
    --to=crquan@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).