All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Pihet <jean.pihet@newoldbits.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@kernel.org>,
	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 spi tree
Date: Wed, 15 Jan 2020 12:38:59 +0100	[thread overview]
Message-ID: <CAORVsuWoLimOmuV59vF_pbRN8msZyjMnVNfAuhuYACXpy_Ffew@mail.gmail.com> (raw)
In-Reply-To: <20200115212739.474e8272@canb.auug.org.au>

Stephen,

On Wed, Jan 15, 2020 at 11:28 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Jean,
>
> On Wed, 15 Jan 2020 10:10:09 +0100 Jean Pihet <jean.pihet@newoldbits.com> wrote:
> >
> > I did not have this warning, it may be a combination of compiler
> > version and build flags. Do you need a fixup patch for it?
>
> That is up to Mark, really.  Unfortunately, Linus will probably get
> this warning during the merge window which he will complain about.

Ok I just sent a fixup patch to Mark (on spi ML). Could it still reach 5.6?

>
> It is really weird, as there are three other references to rx_wlen
> immediately before the one complained about ... so maybe this is a bug
> in the compiler I am using (gcc 9.2.1 from Debian, cross compiler
> ppc64le hosted).
Yes indeed it is weird. Only some compiler versions are throwing the warning.

Thanks,
Jean

>
> --
> Cheers,
> Stephen Rothwell

  reply	other threads:[~2020-01-15 11:39 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  2:23 linux-next: build warning after merge of the spi tree Stephen Rothwell
2020-01-15  9:10 ` Jean Pihet
2020-01-15 10:27   ` Stephen Rothwell
2020-01-15 11:38     ` Jean Pihet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-16  3:11 Stephen Rothwell
2024-02-19 11:18 ` Dhruva Gole
2024-02-08  3:52 Stephen Rothwell
2024-02-08 11:43 ` Mark Brown
2024-02-08 13:32 ` Amadeusz Sławiński
2024-02-08 21:59   ` Stephen Rothwell
2022-06-08  4:30 Stephen Rothwell
2022-06-08  7:30 ` David Jander
2022-06-08 10:05   ` Mark Brown
2021-08-10  6:29 Stephen Rothwell
2021-08-09  5:30 Stephen Rothwell
2021-04-20  3:48 Stephen Rothwell
2021-04-20  7:56 ` Patrice CHOTARD
2021-04-06  6:48 Stephen Rothwell
2021-04-06  7:38 ` Jay Fang
2021-01-11  1:09 Stephen Rothwell
2021-01-04  0:06 Stephen Rothwell
2021-01-04  7:56 ` Ardelean, Alexandru
2020-07-09  4:10 Stephen Rothwell
2020-07-09  5:29 ` Peng Fan
2020-04-28  4:16 Stephen Rothwell
2020-04-28  5:01 ` Sanjay R Mehta
2020-04-28  9:38   ` Mark Brown
2019-04-29  4:30 Stephen Rothwell
2019-01-29  2:02 Stephen Rothwell
2019-01-29  6:57 ` Yogesh Narayan Gaur
2019-01-29  7:25   ` Schrempf Frieder
2019-01-29  8:26   ` Stephen Rothwell
2019-01-29  8:39     ` Yogesh Narayan Gaur
2019-01-10  0:44 Stephen Rothwell
2019-01-10  0:41 Stephen Rothwell
2018-11-14  2:18 Stephen Rothwell
     [not found] ` <CAP6Zq1gp+hmNkvk8D2uv8FUqTXE4+ZMPhMB7A7vLMaM6swHy4g@mail.gmail.com>
2018-11-15 19:26   ` Mark Brown
2018-08-03  4:37 Stephen Rothwell
2017-03-27  2:41 Stephen Rothwell
2017-03-27  5:33 ` Vignesh R
2017-03-27  5:33   ` Vignesh R
2010-10-14  1:59 Stephen Rothwell
2010-10-14  5:00 ` Grant Likely

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=CAORVsuWoLimOmuV59vF_pbRN8msZyjMnVNfAuhuYACXpy_Ffew@mail.gmail.com \
    --to=jean.pihet@newoldbits.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.