From: Steven Whitehouse <swhiteho@redhat.com>
To: Hannes Eder <hannes@hanneseder.net>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] GFS2: fix sparse warning: Should it be static?
Date: Mon, 02 Mar 2009 12:01:56 +0000 [thread overview]
Message-ID: <1235995316.9571.824.camel@quoit> (raw)
In-Reply-To: <20090221011157.5075.6318.stgit@vmbox.hanneseder.net>
Hi,
Applied to the -nmw git tree. Thanks,
Steve.
On Sat, 2009-02-21 at 02:12 +0100, Hannes Eder wrote:
> Impact: Make symbol static.
>
> Fix this sparse warning:
> fs/gfs2/rgrp.c:188:5: warning: symbol 'gfs2_bitfit' was not declared. Should it be static?
>
> Signed-off-by: Hannes Eder <hannes@hanneseder.net>
> ---
> fs/gfs2/rgrp.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
> index 34691d7..f03d024 100644
> --- a/fs/gfs2/rgrp.c
> +++ b/fs/gfs2/rgrp.c
> @@ -185,7 +185,8 @@ static inline u64 gfs2_bit_search(const __le64 *ptr, u64 mask, u8 state)
> * Return: the block number (bitmap buffer scope) that was found
> */
>
> -u32 gfs2_bitfit(const u8 *buf, const unsigned int len, u32 goal, u8 state)
> +static u32 gfs2_bitfit(const u8 *buf, const unsigned int len,
> + u32 goal, u8 state)
> {
> u32 spoint = (goal << 1) & ((8*sizeof(u64)) - 1);
> const __le64 *ptr = ((__le64 *)buf) + (goal >> 5);
>
prev parent reply other threads:[~2009-03-02 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 1:11 [PATCH 0/2] GFS2: fix sparse warnings Hannes Eder
2009-02-21 1:11 ` Hannes Eder
2009-02-21 1:11 ` [PATCH 1/2] GFS2: fix sparse warnings: constant is so big it is Hannes Eder
2009-02-21 1:11 ` Hannes Eder
2009-03-02 12:01 ` [PATCH 1/2] GFS2: fix sparse warnings: constant is so big it Steven Whitehouse
2009-03-02 12:01 ` [PATCH 1/2] GFS2: fix sparse warnings: constant is so big it is Steven Whitehouse
2009-02-21 1:12 ` [PATCH 2/2] GFS2: fix sparse warning: Should it be static? Hannes Eder
2009-02-21 1:12 ` Hannes Eder
2009-03-02 12:01 ` Steven Whitehouse [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=1235995316.9571.824.camel@quoit \
--to=swhiteho@redhat.com \
--cc=hannes@hanneseder.net \
--cc=kernel-janitors@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.