From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: "kernelci.org bot" <bot@kernelci.org>,
"David S. Miller" <davem@davemloft.net>,
tomeu.vizoso@collabora.com, guillaume.tucker@collabora.com,
mgalka@collabora.com, broonie@kernel.org,
matthew.hart@linaro.org, enric.balletbo@collabora.com,
Jose Abreu <joabreu@synopsys.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: next/master boot bisection: next-20190617 on sun8i-h2-plus-orangepi-zero
Date: Tue, 18 Jun 2019 22:42:53 +0200 [thread overview]
Message-ID: <CAFBinCCrpQNU_JtL0SwEGbwWZ2Qy-b2m5rdjuE0__nDRORGTiQ@mail.gmail.com> (raw)
In-Reply-To: <7hr27qdedo.fsf@baylibre.com>
On Tue, Jun 18, 2019 at 6:53 PM Kevin Hilman <khilman@baylibre.com> wrote:
[...]
> This seems to have broken on several sunxi SoCs, but also a MIPS SoC
> (pistachio_marduk):
>
> https://storage.kernelci.org/next/master/next-20190618/mips/pistachio_defconfig/gcc-8/lab-baylibre-seattle/boot-pistachio_marduk.html
today I learned why initializing arrays on the stack is important
too bad gcc didn't warn that I was about to shoot myself (or someone
else) in the foot :/
I just sent a fix: [0]
sorry for this issue and thanks to Kernel CI for even pointing out the
offending commit (this makes things a lot easier than just yelling
that "something is broken")
Martin
[0] https://patchwork.ozlabs.org/patch/1118313/
next prev parent reply other threads:[~2019-06-18 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d089fb6.1c69fb81.4f92.9134@mx.google.com>
2019-06-18 16:53 ` next/master boot bisection: next-20190617 on sun8i-h2-plus-orangepi-zero Kevin Hilman
2019-06-18 20:42 ` Martin Blumenstingl [this message]
2019-06-18 20:53 ` Guillaume Tucker
2019-06-18 20:58 ` Martin Blumenstingl
2019-06-18 21:07 ` Guillaume Tucker
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=CAFBinCCrpQNU_JtL0SwEGbwWZ2Qy-b2m5rdjuE0__nDRORGTiQ@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=joabreu@synopsys.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=matthew.hart@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mgalka@collabora.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=tomeu.vizoso@collabora.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).