From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC][PATCH] btrfs-progs: move sources shared with kernel to own directory
Date: Mon, 3 Oct 2016 18:32:53 +0200 [thread overview]
Message-ID: <20161003163253.GD6576@suse.cz> (raw)
In-Reply-To: <a0920b31-3dad-5253-7d6f-938bb7bedb0b@cn.fujitsu.com>
On Fri, Sep 30, 2016 at 09:11:30AM +0800, Qu Wenruo wrote:
> > - cmds/ - (planned) cmds-*.[ch]
>
> Sounds good, so we can skip the "cmds-" prefix then.
Yes. We have to start somewhere, file renaming is left for later.
>
> > - convert/ - move as-is, split later, eg. per filsystem
> > - image/ - move as-is, split if needed
> > - check/ - split from cmds-check
>
> Pretty cool.
> I'm also moving some code into its own dir doing the user-space scrub work.
> (While I'm creating a new dir called fsck/ and put my scrub code into
> it, rename it to check/ won't be a problem though)
>
> While I'm not sure what is going to be in kernel-shared/ dir.
>
> Uapi headers? or things like disk-io.c volumes.c?
Headers and the files you mentioned. See the branch for complete list.
The headers could be further separated, public and private.
> For uapi headers, then kernel-shared/ may contain few files.
> For disk-io.c/volumes.c, they are not shared with kernel anymore.
Partial sharing should be enough. See changelong:
> > All files that share content and purpose with the corresponding file in
> > the kernel are moved to a separate directory. There's only some overlap,
> > can't be 100% match but many functions are shared. A diff between the
> > files can reveal changes that should be applied to the other codebase.
.
prev parent reply other threads:[~2016-10-03 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 16:38 [RFC][PATCH] btrfs-progs: move sources shared with kernel to own directory David Sterba
2016-09-30 1:11 ` Qu Wenruo
2016-10-03 16:32 ` David Sterba [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=20161003163253.GD6576@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.