From: Mike Frysinger <vapier@gentoo.org>
To: dushistov@mail.ru
Cc: linux-kernel@vger.kernel.org, sparc@gentoo.org
Subject: [patch] export ufs_fs.h to userspace
Date: Thu, 8 Feb 2007 02:46:16 -0500 [thread overview]
Message-ID: <200702080246.16996.vapier@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]
was ufs_fs.h purposefully not exported to userspace or did it just slip
through the cracks ? assuming the latter scenario, the attached patch
touches up the relationship between ufs_fs.h and its sub headers (like
ufs_fs_sb.h) so that we can export it ... the silo bootloader takes advantage
of this header for example
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
---
--- a/include/linux/Kbuild
+++ b/include/linux/Kbuild
@@ -324,6 +324,7 @@ unifdef-y += tty.h
unifdef-y += types.h
unifdef-y += udf_fs_i.h
unifdef-y += udp.h
+unifdef-y += ufs_fs.h
unifdef-y += uinput.h
unifdef-y += uio.h
unifdef-y += unistd.h
--- a/include/linux/ufs_fs.h
+++ b/include/linux/ufs_fs.h
@@ -45,8 +45,10 @@ typedef __u32 __bitwise __fs32;
typedef __u16 __bitwise __fs16;
#endif
+#ifdef __KERNEL__
#include <linux/ufs_fs_i.h>
#include <linux/ufs_fs_sb.h>
+#endif
#define UFS_BBLOCK 0
#define UFS_BBSIZE 8192
@@ -303,7 +305,7 @@ typedef __u16 __bitwise __fs16;
#define UFS_MAXMNTLEN 512
#define UFS2_MAXMNTLEN 468
#define UFS2_MAXVOLLEN 32
-/* #define UFS_MAXCSBUFS 31 */
+#define UFS_MAXCSBUFS 31
#define UFS_LINK_MAX 32000
/*
#define UFS2_NOCSPTRS ((128 / sizeof(void *)) - 4)
--- a/include/linux/ufs_fs_sb.h
+++ b/include/linux/ufs_fs_sb.h
@@ -21,7 +21,6 @@
struct ufs_sb_private_info;
struct ufs_cg_private_info;
struct ufs_csum;
-#define UFS_MAXCSBUFS 31
struct ufs_sb_info {
struct ufs_sb_private_info * s_uspi;
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next reply other threads:[~2007-02-08 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 7:46 Mike Frysinger [this message]
2007-02-08 10:33 ` [patch] export ufs_fs.h to userspace Arjan van de Ven
2007-02-08 11:33 ` Alexey Dobriyan
2007-02-08 15:10 ` Mike Frysinger
2007-02-08 15:59 ` Arjan van de Ven
2007-02-08 16:12 ` Mike Frysinger
2007-02-08 20:02 ` Christoph Hellwig
2007-02-08 20:05 ` Mike Frysinger
2007-02-08 20:21 ` 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=200702080246.16996.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=dushistov@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=sparc@gentoo.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