cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs/gfs_mkfs device_geometry.c fs_geom ...
Date: 21 Aug 2006 19:11:23 -0000	[thread overview]
Message-ID: <20060821191123.11501.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	rpeterso at sourceware.org	2006-08-21 19:11:22

Modified files:
	gfs/gfs_mkfs   : device_geometry.c fs_geometry.c locking.c 
	                 main.c ondisk.c structures.c 

Log message:
	Get gfs_ondisk.h from local includes, not kernel includes.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_mkfs/device_geometry.c.diff?cvsroot=cluster&r1=1.3&r2=1.4
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_mkfs/fs_geometry.c.diff?cvsroot=cluster&r1=1.2&r2=1.3
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_mkfs/locking.c.diff?cvsroot=cluster&r1=1.1&r2=1.2
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_mkfs/main.c.diff?cvsroot=cluster&r1=1.4&r2=1.5
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_mkfs/ondisk.c.diff?cvsroot=cluster&r1=1.2&r2=1.3
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_mkfs/structures.c.diff?cvsroot=cluster&r1=1.4&r2=1.5

--- cluster/gfs/gfs_mkfs/device_geometry.c	2006/07/10 23:39:35	1.3
+++ cluster/gfs/gfs_mkfs/device_geometry.c	2006/08/21 19:11:22	1.4
@@ -25,7 +25,7 @@
 #include <sys/param.h>
 
 #include "global.h"
-#include <linux/gfs_ondisk.h>
+#include "gfs_ondisk.h"
 #include "osi_list.h"
 #include "mkfs_gfs.h"
 #include "libgfs.h"
--- cluster/gfs/gfs_mkfs/fs_geometry.c	2006/07/10 23:39:35	1.2
+++ cluster/gfs/gfs_mkfs/fs_geometry.c	2006/08/21 19:11:22	1.3
@@ -24,7 +24,7 @@
 #include <time.h>
 
 #include "global.h"
-#include <linux/gfs_ondisk.h>
+#include "gfs_ondisk.h"
 #include "osi_list.h"
 
 #include "mkfs_gfs.h"
--- cluster/gfs/gfs_mkfs/locking.c	2004/06/24 08:53:23	1.1
+++ cluster/gfs/gfs_mkfs/locking.c	2006/08/21 19:11:22	1.2
@@ -17,7 +17,7 @@
 #include <ctype.h>
 
 #include "global.h"
-#include <linux/gfs_ondisk.h>
+#include "gfs_ondisk.h"
 #include "osi_list.h"
 
 #include "mkfs_gfs.h"
--- cluster/gfs/gfs_mkfs/main.c	2006/07/10 23:39:35	1.4
+++ cluster/gfs/gfs_mkfs/main.c	2006/08/21 19:11:22	1.5
@@ -24,7 +24,7 @@
 #include <time.h>
 
 #include "global.h"
-#include <linux/gfs_ondisk.h>
+#include "gfs_ondisk.h"
 #include "osi_list.h"
 #include "libvolume_id.h"
 #include "libgfs.h"
--- cluster/gfs/gfs_mkfs/ondisk.c	2005/01/18 16:19:00	1.2
+++ cluster/gfs/gfs_mkfs/ondisk.c	2006/08/21 19:11:22	1.3
@@ -16,7 +16,6 @@
 
 #include "global.h"
 #include "linux_endian.h"
-#include <linux/gfs_ondisk.h>
 
 #define printk printf
 #define pv(struct, member, fmt) printf("  "#member" = "fmt"\n", struct->member);
@@ -27,5 +26,5 @@
 #define RETURN(x, y) return y
 
 #define WANT_GFS_CONVERSION_FUNCTIONS
-#include <linux/gfs_ondisk.h>
+#include "gfs_ondisk.h"
 
--- cluster/gfs/gfs_mkfs/structures.c	2006/07/14 19:28:26	1.4
+++ cluster/gfs/gfs_mkfs/structures.c	2006/08/21 19:11:22	1.5
@@ -24,7 +24,7 @@
 #include <time.h>
 
 #include "global.h"
-#include <linux/gfs_ondisk.h>
+#include "gfs_ondisk.h"
 #include "osi_list.h"
 #include "linux_endian.h"
 #include "libgfs.h"



                 reply	other threads:[~2006-08-21 19:11 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=20060821191123.11501.qmail@sourceware.org \
    --to=rpeterso@sourceware.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).