From: Anna Schumaker <schumaker.anna@gmail.com>
To: David Wysochanski <dwysocha@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Anna Schumaker <Anna.Schumaker@Netapp.com>,
Trond Myklebust <trondmy@gmail.com>,
NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the nfs-anna tree
Date: Tue, 31 Jul 2018 09:46:52 -0400 [thread overview]
Message-ID: <35966b8f-43c9-ed1c-215e-f26a0fc1395b@gmail.com> (raw)
In-Reply-To: <1533027885.3710.2.camel@redhat.com>
Hi David,
On 07/31/2018 05:04 AM, David Wysochanski wrote:
> On Mon, 2018-07-30 at 18:52 +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the nfs-anna tree, today's linux-next build (powerpc
>> ppc44x_defconfig, sparc defconfig) produced this warning:
>>
>> net/sunrpc/stats.c: In function 'rpc_clnt_show_stats':
>> /home/sfr/next/next/net/sunrpc/stats.c:258:32: warning: excess elements in struct initializer
>> struct rpc_iostats stats = { 0 };
>>
>
> Apologies I did not see this before submission.
>
> The below fixup compiles without warning for me on ppc64le.
>
> struct rpc_iostats stats = {};
Can you resend the patch with that change, please?
Thanks,
Anna
>
>
>> ^
>>
>> Introduced by commit
>>
>> c3b588a2d5be ("sunrpc: Change rpc_print_iostats to rpc_clnt_show_stats and handle rpc_clnt clones")
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2018-07-31 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 8:52 linux-next: build warning after merge of the nfs-anna tree Stephen Rothwell
2018-07-31 9:04 ` David Wysochanski
2018-07-31 13:46 ` Anna Schumaker [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-24 4:46 Stephen Rothwell
2024-09-24 17:08 ` Mike Snitzer
2025-01-09 4:23 Stephen Rothwell
2025-01-14 5:45 ` Stephen Rothwell
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=35966b8f-43c9-ed1c-215e-f26a0fc1395b@gmail.com \
--to=schumaker.anna@gmail.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=dwysocha@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trondmy@gmail.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;
as well as URLs for NNTP newsgroup(s).