linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: al@alarsen.net, linux-kernel@vger.kernel.org
Subject: [2.6 patch] fs/qnx4/: make some code static
Date: Fri, 25 Feb 2005 00:37:11 +0100	[thread overview]
Message-ID: <20050224233711.GO8651@stusta.de> (raw)

This patch makes some needlessly global code static.

Signed-off-by: Adrian Bunk <bunk@stusta.de>

---

This patch was already sent on:
- 8 Jan 2005

 fs/qnx4/bitmap.c        |    4 ++--
 fs/qnx4/inode.c         |    8 ++++----
 include/linux/qnx4_fs.h |    2 --
 3 files changed, 6 insertions(+), 8 deletions(-)

--- linux-2.6.10-mm2-full/fs/qnx4/bitmap.c.old	2005-01-08 17:14:26.000000000 +0100
+++ linux-2.6.10-mm2-full/fs/qnx4/bitmap.c	2005-01-08 17:14:38.000000000 +0100
@@ -28,8 +28,8 @@
 	return 0;
 }
 
-void count_bits(register const char *bmPart, register int size,
-		int *const tf)
+static void count_bits(register const char *bmPart, register int size,
+		       int *const tf)
 {
 	char b;
 	int tot = *tf;
--- linux-2.6.10-mm2-full/include/linux/qnx4_fs.h.old	2005-01-08 17:15:37.000000000 +0100
+++ linux-2.6.10-mm2-full/include/linux/qnx4_fs.h	2005-01-08 17:15:52.000000000 +0100
@@ -114,7 +114,6 @@
 extern unsigned long qnx4_count_free_blocks(struct super_block *sb);
 extern unsigned long qnx4_block_map(struct inode *inode, long iblock);
 
-extern struct buffer_head *qnx4_getblk(struct inode *, int, int);
 extern struct buffer_head *qnx4_bread(struct inode *, int, int);
 
 extern struct inode_operations qnx4_file_inode_operations;
@@ -130,7 +129,6 @@
 extern int qnx4_rmdir(struct inode *dir, struct dentry *dentry);
 extern int qnx4_sync_file(struct file *file, struct dentry *dentry, int);
 extern int qnx4_sync_inode(struct inode *inode);
-extern int qnx4_get_block(struct inode *inode, sector_t iblock, struct buffer_head *bh, int create);
 
 static inline struct qnx4_sb_info *qnx4_sb(struct super_block *sb)
 {
--- linux-2.6.10-mm2-full/fs/qnx4/inode.c.old	2005-01-08 17:15:01.000000000 +0100
+++ linux-2.6.10-mm2-full/fs/qnx4/inode.c	2005-01-08 17:16:08.000000000 +0100
@@ -162,8 +162,8 @@
 	return 0;
 }
 
-struct buffer_head *qnx4_getblk(struct inode *inode, int nr,
-				 int create)
+static struct buffer_head *qnx4_getblk(struct inode *inode, int nr,
+				       int create)
 {
 	struct buffer_head *result = NULL;
 
@@ -212,7 +212,7 @@
 	return NULL;
 }
 
-int qnx4_get_block( struct inode *inode, sector_t iblock, struct buffer_head *bh, int create )
+static int qnx4_get_block( struct inode *inode, sector_t iblock, struct buffer_head *bh, int create )
 {
 	unsigned long phys;
 
@@ -447,7 +447,7 @@
 {
 	return generic_block_bmap(mapping,block,qnx4_get_block);
 }
-struct address_space_operations qnx4_aops = {
+static struct address_space_operations qnx4_aops = {
 	.readpage	= qnx4_readpage,
 	.writepage	= qnx4_writepage,
 	.sync_page	= block_sync_page,


             reply	other threads:[~2005-02-24 23:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 23:37 Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-08 22:03 [2.6 patch] fs/qnx4/: make some code static Adrian Bunk

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=20050224233711.GO8651@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=al@alarsen.net \
    --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;
as well as URLs for NNTP newsgroup(s).