linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Darrick J . Wong" <darrick.wong@oracle.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH] xfs: Add missing braces around xfs_scrub_agfl_info initializer
Date: Thu,  1 Feb 2018 11:23:04 +0100	[thread overview]
Message-ID: <1517480584-4588-1-git-send-email-geert@linux-m68k.org> (raw)

With gcc-4.1.2:

    fs/xfs/scrub/agheader.c: In function ‘xfs_scrub_agfl’:
    fs/xfs/scrub/agheader.c:770: warning: missing braces around initializer
    fs/xfs/scrub/agheader.c:770: warning: (near initialization for ‘sai.oinfo’)

The first member of struct xfs_scrub_agfl_info is no longer an integral
type, but a struct.  Add the missing curly braces to fix this.

Fixes: d852657ccfc0e455 ("xfs: cross-reference reverse-mapping btree")
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
 fs/xfs/scrub/agheader.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/xfs/scrub/agheader.c b/fs/xfs/scrub/agheader.c
index fd975524f4603387..9bcfdb0d1da379f5 100644
--- a/fs/xfs/scrub/agheader.c
+++ b/fs/xfs/scrub/agheader.c
@@ -767,7 +767,7 @@ int
 xfs_scrub_agfl(
 	struct xfs_scrub_context	*sc)
 {
-	struct xfs_scrub_agfl_info	sai = { 0 };
+	struct xfs_scrub_agfl_info	sai = { { 0 } };
 	struct xfs_agf			*agf;
 	xfs_agnumber_t			agno;
 	unsigned int			agflcount;
-- 
2.7.4

             reply	other threads:[~2018-02-01 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 10:23 Geert Uytterhoeven [this message]
2018-02-01 11:31 ` [PATCH] xfs: Add missing braces around xfs_scrub_agfl_info initializer Arnd Bergmann
2018-02-01 17:08   ` Darrick J. Wong
2018-02-01 17:24     ` Joe Perches

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=1517480584-4588-1-git-send-email-geert@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=darrick.wong@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).