From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42986] ext2_fs.h requires undefined type umode_t
Date: Fri, 13 Apr 2012 06:48:53 GMT [thread overview]
Message-ID: <201204130648.q3D6mrb3007044@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42986-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42986
Artem Bityutskiy <dedekind1@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dedekind1@gmail.com
--- Comment #15 from Artem Bityutskiy <dedekind1@gmail.com> 2012-04-13 06:48:52 ---
(In reply to comment #13)
> For the record: busybox's mkfs_ext2.c uses linux/ext2_fs.h.
> If its include is commented out, the following errors pop out:
The idea is that file-system on-disk layout is stable, so it should be easy for
you to have a copy, and you do not need to ever update it unless you add
support of a new feature in busybox which requeres an up-to-date header file,
and this should be a rare event.
>From the FS'es POW - the on-disk layout is not kernel-userspace API so kernel
should not export it to user-space. This will also make things easier for the
kernel people - we can freely clean-up/rename/shuffle things in the header
without being afraid of breaking busybox or any other tool.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
prev parent reply other threads:[~2012-04-13 6:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 13:23 [Bug 42986] New: ext2_fs.h requires undefined type umode_t bugzilla-daemon
2012-03-24 14:04 ` [Bug 42986] " bugzilla-daemon
2012-03-24 14:16 ` bugzilla-daemon
2012-03-25 1:20 ` bugzilla-daemon
2012-03-25 2:47 ` bugzilla-daemon
2012-03-25 17:21 ` bugzilla-daemon
2012-03-27 4:41 ` bugzilla-daemon
2012-03-27 5:02 ` bugzilla-daemon
2012-03-27 5:33 ` bugzilla-daemon
2012-03-27 7:31 ` Christoph Hellwig
2012-03-27 5:58 ` bugzilla-daemon
2012-03-27 6:05 ` bugzilla-daemon
2012-03-27 6:17 ` bugzilla-daemon
2012-03-27 6:21 ` bugzilla-daemon
2012-04-12 11:37 ` bugzilla-daemon
2012-04-12 15:04 ` bugzilla-daemon
2012-04-13 6:48 ` bugzilla-daemon [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=201204130648.q3D6mrb3007044@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).