From: Dave Chinner <david@fromorbit.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: xfs@oss.sgi.com, bfoster@redhat.com, sandeen@sandeen.net,
hch@lst.de, jack@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/12] xfs:Make the function,xfs_alloc_lookup_eq static
Date: Wed, 6 May 2015 08:12:09 +1000 [thread overview]
Message-ID: <20150505221209.GG21261@dastard> (raw)
In-Reply-To: <1430856999-31952-1-git-send-email-xerofoify@gmail.com>
On Tue, May 05, 2015 at 04:16:28PM -0400, Nicholas Krause wrote:
> This makes the function,xfs_alloc_lookup_eq static as there are no
> calls to this function outside the definition file for this function,
> xfs_alloc.c.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> fs/xfs/libxfs/xfs_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/libxfs/xfs_alloc.c b/fs/xfs/libxfs/xfs_alloc.c
> index 516162b..48de3f0 100644
> --- a/fs/xfs/libxfs/xfs_alloc.c
> +++ b/fs/xfs/libxfs/xfs_alloc.c
> @@ -52,7 +52,7 @@ STATIC int xfs_alloc_ag_vextent_small(xfs_alloc_arg_t *,
> /*
> * Lookup the record equal to [bno, len] in the btree given by cur.
> */
> -STATIC int /* error */
> +static int /* error */
> xfs_alloc_lookup_eq(
> struct xfs_btree_cur *cur, /* btree cursor */
> xfs_agblock_t bno, /* starting block of extent */
Please have a look at what STATIC actually means, and then use the
sparse checker to confirm that these functions are already static
for a CONFIG_XFS_DEBUG=n build.
i.e. STATIC is a stack usage minimisation and debugging aid, not
something that is broken and needs fixing.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2015-05-05 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430856999-31952-1-git-send-email-xerofoify@gmail.com>
2015-05-05 20:18 ` [PATCH 01/12] xfs:Make the function,xfs_alloc_lookup_eq static Christoph Hellwig
2015-05-05 22:12 ` Dave Chinner [this message]
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=20150505221209.GG21261@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=xerofoify@gmail.com \
--cc=xfs@oss.sgi.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