public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>,
	Joel Becker <joel.becker@oracle.com>,
	Mark Fasheh <mark.fasheh@oracle.com>,
	Kurt Hackel <kurt.hackel@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: [-mm patch] fs/ocfs2/file.c: make ocfs2_extend_allocation() static
Date: Fri, 11 Nov 2005 17:40:53 +0100	[thread overview]
Message-ID: <20051111164053.GM5376@stusta.de> (raw)
In-Reply-To: <20051110203544.027e992c.akpm@osdl.org>

On Thu, Nov 10, 2005 at 08:35:44PM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.14-mm1:
>...
>  git-ocfs2.patch
>...
>  Subsystem trees
>...


<--  snip  -->


This patch makes the needlessly  global function 
ocfs2_extend_allocation() static.


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

--- linux-2.6.14-mm2-full/fs/ocfs2/file.c.old	2005-11-11 16:55:01.000000000 +0100
+++ linux-2.6.14-mm2-full/fs/ocfs2/file.c	2005-11-11 16:55:19.000000000 +0100
@@ -413,8 +413,8 @@
 	return status;
 }
 
-int ocfs2_extend_allocation(struct inode *inode,
-			    u32 clusters_to_add)
+static int ocfs2_extend_allocation(struct inode *inode,
+				   u32 clusters_to_add)
 {
 	int status = 0;
 	int restart_func = 0;


  parent reply	other threads:[~2005-11-11 16:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11  4:35 2.6.14-mm2 Andrew Morton
2005-11-11  5:23 ` 2.6.14-mm2: loop detected in depmod Brice Goglin
2005-11-11  7:52   ` Antonino A. Daplas
2005-11-12  3:41     ` Brice Goglin
2005-11-11  5:49 ` 2.6.14-mm2 Reuben Farrelly
2005-11-11  6:07   ` 2.6.14-mm2 Andrew Morton
2005-11-11  8:28     ` 2.6.14-mm2 Reuben Farrelly
2005-11-11  8:55       ` 2.6.14-mm2 Andrew Morton
2005-11-11 13:28         ` 2.6.14-mm2 Reuben Farrelly
2005-11-11  8:54 ` 2.6.14-mm2 J.A. Magallon
2005-11-11 12:33 ` 2.6.14-mm2 Felipe Alfaro Solana
2005-11-11 16:40 ` Adrian Bunk [this message]
2005-11-11 17:09 ` [-mm PATCH] slob: add kmem_set_shrinker Yoichi Yuasa
2005-11-11 19:14 ` 2.6.14-mm2 Badari Pulavarty
2005-11-11 19:21   ` 2.6.14-mm2 Andrew Morton
2005-11-11 19:32     ` 2.6.14-mm2 Badari Pulavarty
2005-11-11 22:32 ` 2.6.14-mm2 Michal Piotrowski
2005-11-11 22:37   ` 2.6.14-mm2 Michal Piotrowski
2005-11-11 23:01   ` 2.6.14-mm2 Andrew Morton
2005-11-11 23:28     ` [PATCH] nvidiafb: Fix bug in nvidiafb_pan_display Antonino A. Daplas
2005-11-11 23:38       ` Benjamin Herrenschmidt
2005-11-11 23:55         ` Antonino A. Daplas
2005-11-11 23:54       ` Michal Piotrowski
2005-11-11 23:30     ` 2.6.14-mm2 Michal Piotrowski
2005-11-12  0:45       ` 2.6.14-mm2 Antonino A. Daplas
2005-11-16  9:04 ` 2.6.14-mm2 KAMEZAWA Hiroyuki
2005-11-16 12:56 ` 2.6.14-mm2 KAMEZAWA Hiroyuki
2005-11-16 13:17   ` [Lhms-devel] 2.6.14-mm2 Dave Hansen
2005-11-16 16:02     ` Kamezawa Hiroyuki
2005-11-16 16:31       ` Dave Hansen
2005-11-16 16:39         ` Kamezawa Hiroyuki
2005-11-17  0:10         ` KAMEZAWA Hiroyuki
2005-11-17  9:16         ` KAMEZAWA Hiroyuki
  -- strict thread matches above, loose matches on Subject: below --
2005-12-11 21:54 [-mm patch] fs/ocfs2/file.c: make ocfs2_extend_allocation() static Adrian Bunk
2005-12-12  7:27 ` Joel Becker

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=20051111164053.GM5376@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=joel.becker@oracle.com \
    --cc=kurt.hackel@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    /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