From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Oleg Drokin <green@clusterfs.com>,
linux-kernel@vger.kernel.org, braam@clusterfs.com
Subject: [2.6 patch] #ifndef guard percpu_counter.h and blockgroup_lock.h
Date: Mon, 12 Jul 2004 01:06:15 +0200 [thread overview]
Message-ID: <20040711230615.GF4701@fs.tum.de> (raw)
Insert header guards to allow possible multiple inclusion for
include/linux/percpu_counter.h and include/linux/blockgroup_lock.h
This patch is basically
[6/9] Lustre VFS patches for 2.6
by Oleg Drokin <green@clusterfs.com> with the exception that I put the
#ifndef's before the initial comments.
Independent of the Lustre discussions this patch seems to be a good
idea.
diffstat output:
include/linux/blockgroup_lock.h | 4 +++-
include/linux/percpu_counter.h | 4 ++++
2 files changed, 7 insertions(+), 1 deletion(-)
Signed-off-by: Adrian Bunk <bunk@fs.tum.de>
--- linux-2.6.7-mm7-full/include/linux/percpu_counter.h.old 2004-07-12 00:58:09.000000000 +0200
+++ linux-2.6.7-mm7-full/include/linux/percpu_counter.h 2004-07-12 01:01:11.000000000 +0200
@@ -1,3 +1,5 @@
+#ifndef _LINUX_PERCPU_COUNTER_H
+#define _LINUX_PERCPU_COUNTER_H
/*
* A simple "approximate counter" for use in ext2 and ext3 superblocks.
*
@@ -101,3 +103,5 @@
{
percpu_counter_mod(fbc, -1);
}
+
+#endif /* _LINUX_PERCPU_COUNTER_H */
--- linux-2.6.7-mm7-full/include/linux/blockgroup_lock.h.old 2004-07-12 00:59:38.000000000 +0200
+++ linux-2.6.7-mm7-full/include/linux/blockgroup_lock.h 2004-07-12 01:01:17.000000000 +0200
@@ -1,3 +1,5 @@
+#ifndef _LINUX_BLOCKGROUP_LOCK_H
+#define _LINUX_BLOCKGROUP_LOCK_H
/*
* Per-blockgroup locking for ext2 and ext3.
*
@@ -55,4 +57,4 @@
#define sb_bgl_lock(sb, block_group) \
(&(sb)->s_blockgroup_lock.locks[(block_group) & (NR_BG_LOCKS-1)].lock)
-
+#endif
reply other threads:[~2004-07-11 23:06 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=20040711230615.GF4701@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=braam@clusterfs.com \
--cc=green@clusterfs.com \
--cc=linux-kernel@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