From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Long Li <longli@microsoft.com>,
Pavel Shilovsky <pshilov@microsoft.com>,
Ronnie Sahlberg <lsahlber@redhat.com>
Subject: Re: linux-next: build warning after merge of the cifs tree
Date: Thu, 4 Jan 2018 16:52:17 +1100 [thread overview]
Message-ID: <20180104165217.7737a0bc@canb.auug.org.au> (raw)
In-Reply-To: <CAH2r5mvgtC3Y_aLxk7-_R8E=ohR1LoFSkiqZZ6rhn9azXY05xw@mail.gmail.com>
Hi Steve,
On Wed, 3 Jan 2018 16:44:59 -0600 Steve French <smfrench@gmail.com> wrote:
>
> I don't see this with gcc 5.4
Good to know.
> Harmless to initialize flags here ... even if unneeded ... so if it
> makes your life easier I don't mind initializes to 0. Let me know.
> Wonder why it doesn't generate the warning on the various other places
> in the fs that do the same thing?
I might just take the hint to upgrade my cross compilers :-) Thanks anyway.
In the mean time, my scripts will automatically skip reporting this
warning to me.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2018-01-04 5:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 22:33 Stephen Rothwell
2018-01-03 22:44 ` Steve French
2018-01-04 5:52 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-05 6:05 Stephen Rothwell
2025-06-05 13:42 ` Meetakshi Setiya
2025-06-05 15:38 ` Steve French
2024-01-19 1:47 Stephen Rothwell
2024-01-19 3:02 ` Steve French
2022-05-23 0:57 Stephen Rothwell
2022-05-23 2:29 ` Steve French
2021-02-04 22:51 Stephen Rothwell
2019-07-18 23:16 Stephen Rothwell
2019-07-18 23:38 ` Steve French
2017-11-20 23:19 Stephen Rothwell
2017-11-20 23:37 ` Steve French
2017-06-26 0:07 Stephen Rothwell
2017-06-26 16:57 ` Steve French
2011-01-31 2:30 Stephen Rothwell
2011-01-31 10:49 ` Suresh Jayaraman
2011-01-31 11:38 ` Pavel Shilovsky
2011-01-31 12:29 ` Jeff Layton
2011-01-31 2:27 Stephen Rothwell
2011-01-31 3:25 ` Steve French
2011-01-31 2:25 Stephen Rothwell
2011-01-21 1:05 Stephen Rothwell
2011-01-21 1:20 ` Jeff Layton
2010-09-24 3:55 Stephen Rothwell
2010-10-19 5:21 ` Stephen Rothwell
2010-10-19 13:13 ` Jeff Layton
2010-10-19 15:48 ` Shirish Pargaonkar
2010-09-24 3:48 Stephen Rothwell
2010-09-24 11:13 ` Jeff Layton
2010-08-26 1:02 Stephen Rothwell
2010-08-26 2:07 ` Steve French
2010-04-01 0:50 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=20180104165217.7737a0bc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=lsahlber@redhat.com \
--cc=pshilov@microsoft.com \
--cc=smfrench@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
all inboxes | Powered by JetHome®