From: Yegor Yefremov <yegorslists@googlemail.com>
To: barebox <barebox@lists.infradead.org>
Subject: Re: [RFC] fs: move super_block and inode definitions to central fs.h header
Date: Sun, 24 Jan 2016 20:55:22 +0100 [thread overview]
Message-ID: <CAGm1_ksoy5BweOmR1FYaTG4=C4jZnxtvaBgukpbasJv6tDGSkA@mail.gmail.com> (raw)
In-Reply-To: <1453663456-5168-1-git-send-email-yegorslists@googlemail.com>
On Sun, Jan 24, 2016 at 8:24 PM, Yegor Yefremov
<yegorslists@googlemail.com> wrote:
> Both super_block and inode are common to various file systems, so
> move them to the central place.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> fs/ubifs/ubifs.h | 134 +------------------------------------------------------
> include/fs.h | 134 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 135 insertions(+), 133 deletions(-)
I'm trying to port SquashFS to Barebox. SquashFS uses at least both
super_block structure as also inode structure. Does it make sense to
introduce include/linux/fs.h?
What to do with struct timespec? It is defined in uapi part. Should it
go to include/linux/barebox-wrapper.h?
Yegor
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-01-24 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 19:24 Yegor Yefremov
2016-01-24 19:55 ` Yegor Yefremov [this message]
2016-01-25 8:20 ` Sascha Hauer
2016-01-25 8:40 ` Yegor Yefremov
2016-01-25 8:47 ` Sascha Hauer
2016-01-25 8:49 ` Yegor Yefremov
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='CAGm1_ksoy5BweOmR1FYaTG4=C4jZnxtvaBgukpbasJv6tDGSkA@mail.gmail.com' \
--to=yegorslists@googlemail.com \
--cc=barebox@lists.infradead.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