From: Bob Peterson <rpeterso@redhat.com>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel@vger.kernel.org,
Steven Whitehouse <swhiteho@redhat.com>,
cluster-devel@redhat.com
Subject: Re: [PATCH V2 linux-next] gfs2: fix shadow warning in gfs2_rbm_find()
Date: Mon, 18 May 2015 16:37:35 -0400 (EDT) [thread overview]
Message-ID: <661277919.1072061.1431981455435.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1431975184-1096-1-git-send-email-fabf@skynet.be>
----- Original Message -----
> bi was already declared and initialized globally in gfs2_rbm_find()
>
> Suggested-by: Bob Peterson <rpeterso@redhat.com>
> Signed-off-by: Fabian Frederick <fabf@skynet.be>
> ---
> V2: use global bi instead of new call to rbm_bi()
> on local variable.
>
> fs/gfs2/rgrp.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
> index 900e515..cd53d6e 100644
> --- a/fs/gfs2/rgrp.c
> +++ b/fs/gfs2/rgrp.c
> @@ -1711,10 +1711,8 @@ static int gfs2_rbm_find(struct gfs2_rbm *rbm, u8
> state, u32 *minext,
> return ret;
>
> bitmap_full: /* Mark bitmap as full and fall through */
> - if ((state == GFS2_BLKST_FREE) && initial_offset == 0) {
> - struct gfs2_bitmap *bi = rbm_bi(rbm);
> + if ((state == GFS2_BLKST_FREE) && initial_offset == 0)
> set_bit(GBF_FULL, &bi->bi_flags);
> - }
>
> next_bitmap: /* Find next bitmap in the rgrp */
> rbm->offset = 0;
> --
> 2.4.0
Hi,
Thanks. This is now applied to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=a3e3213676d8208328ef9f79936f94e583c0ec90
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2015-05-18 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 18:53 Fabian Frederick
2015-05-18 20:37 ` Bob Peterson [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=661277919.1072061.1431981455435.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.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
all inboxes | Powered by JetHome®