public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: David Chinner <david@fromorbit•com>,
	xfs-masters@oss•sgi.com, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org, Christoph Hellwig <hch@lst•de>,
	Felix Blyakher <felixb@sgi•com>
Subject: [PATCH] un-static xfs_read_agf
Date: Thu, 02 Jul 2009 21:35:43 -0500	[thread overview]
Message-ID: <4A4D6E7F.4060204@sandeen.net> (raw)
In-Reply-To: <20090703100551.e3f21aa0.sfr@canb.auug.org.au>

CONFIG_XFS_DEBUG builds still need xfs_read_agf to be
non-static, oops.

Signed-off-by: Eric Sandeen <sandeen@sandeen•net>
---

Index: linux-2.6/fs/xfs/xfs_ag.h
===================================================================
--- linux-2.6.orig/fs/xfs/xfs_ag.h
+++ linux-2.6/fs/xfs/xfs_ag.h
@@ -91,6 +91,9 @@ typedef struct xfs_agf {
 #define	XFS_AGF_BLOCK(mp)	XFS_HDR_BLOCK(mp, XFS_AGF_DADDR(mp))
 #define	XFS_BUF_TO_AGF(bp)	((xfs_agf_t *)XFS_BUF_PTR(bp))
 
+extern int xfs_read_agf(struct xfs_mount *mp, struct xfs_trans *tp,
+			xfs_agnumber_t agno, int flags, struct xfs_buf **bpp);
+
 /*
  * Size of the unlinked inode hash table in the agi.
  */
Index: linux-2.6/fs/xfs/xfs_alloc.c
===================================================================
--- linux-2.6.orig/fs/xfs/xfs_alloc.c
+++ linux-2.6/fs/xfs/xfs_alloc.c
@@ -2248,7 +2248,7 @@ xfs_alloc_put_freelist(
 /*
  * Read in the allocation group header (free/alloc section).
  */
-STATIC int				/* error */
+int					/* error */
 xfs_read_agf(
 	struct xfs_mount	*mp,	/* mount point structure */
 	struct xfs_trans	*tp,	/* transaction pointer */

  reply	other threads:[~2009-07-03  2:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03  0:05 linux-next: xfs tree build failure Stephen Rothwell
2009-07-03  2:35 ` Eric Sandeen [this message]
2009-07-03  4:45   ` [PATCH] un-static xfs_read_agf Felix Blyakher

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=4A4D6E7F.4060204@sandeen.net \
    --to=sandeen@sandeen$(echo .)net \
    --cc=david@fromorbit$(echo .)com \
    --cc=felixb@sgi$(echo .)com \
    --cc=hch@lst$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=xfs-masters@oss$(echo .)sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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