From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Takashi Iwai <tiwai@suse.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
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 Linus' tree
Date: Mon, 29 Jul 2019 18:20:08 +1000 [thread overview]
Message-ID: <20190729182008.14e75363@canb.auug.org.au> (raw)
In-Reply-To: <s5h5znlpbdt.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Hi all,
On Mon, 29 Jul 2019 09:07:10 +0200 Takashi Iwai <tiwai@suse.de> wrote:
>
> On Mon, 29 Jul 2019 09:03:14 +0200,
> Johannes Berg wrote:
> >
> > On Mon, 2019-07-29 at 08:58 +0200, Takashi Iwai wrote:
> > > > This warning has been around for a long time. It could possibly be
> > > > suppressed by checking for errors returned by onyx_read_register().
> > >
> > > Yes, or simply zero-ing the variable in onyx_read_register(). The
> > > current code ignores the read error and it's been OK over a decade :)
> >
> > Yeah, it's pretty weird that it never showed up before. I was wondering
> > for a minute why I was CC'ed on a sound merge issue :-)
>
> Maybe switched to a new gcc version?
Or the number of warnings in a powerpc allyesconfig build got low
enough for me to finally take notice :-)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-29 8:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 4:04 linux-next: build warning after merge of Linus' tree Stephen Rothwell
2019-07-29 6:58 ` Takashi Iwai
2019-07-29 7:03 ` Johannes Berg
2019-07-29 7:07 ` Takashi Iwai
2019-07-29 8:20 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-01 7:18 Stephen Rothwell
2021-10-01 16:33 ` Eric Dumazet
2021-10-05 9:18 Stephen Rothwell
2021-10-05 10:10 ` Jeff Layton
2021-11-23 5:29 Stephen Rothwell
2022-01-20 3:27 ` Stephen Rothwell
2023-05-08 4:44 Stephen Rothwell
2023-05-08 6:28 ` Sakari Ailus
2024-03-13 4:04 Stephen Rothwell
2024-10-01 3:47 Stephen Rothwell
2024-10-01 15:02 ` Christian Brauner
2025-03-05 9:46 Stephen Rothwell
2025-04-22 10:47 Stephen Rothwell
2025-04-22 15:59 ` Linus Torvalds
2025-04-22 17:50 ` Thomas Weißschuh
2025-04-22 18:20 ` Linus Torvalds
2025-04-22 20:48 ` Nathan Chancellor
2025-04-22 20:49 ` Linus Torvalds
2025-04-27 11:42 ` David Laight
2025-04-22 23:55 ` Stephen Rothwell
2025-11-27 2:10 Stephen Rothwell
2025-12-16 1:08 ` 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=20190729182008.14e75363@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tiwai@suse.de \
/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