From: Linus Walleij <linus.walleij@linaro.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Linux PM list <linux-pm@vger.kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Elaine Zhang <zhangqing@rock-chips.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eduardo Valentin <edubezval@gmail.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Mark Brown <broonie@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Matt Hart <matthew.hart@linaro.org>,
mgalka@collabora.com,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Zhang Rui <rui.zhang@intel.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: linusw/for-next boot bisection: v5.2-rc1-8-g73a790c68d7e on rk3288-veyron-jaq
Date: Tue, 28 May 2019 10:45:13 +0200 [thread overview]
Message-ID: <CACRpkdb-Dv614V7STLRMpiLkmb_7NVyKnh2oUi=7Rx366tmZ-A@mail.gmail.com> (raw)
In-Reply-To: <de92e3bd-70e8-fcba-3c88-c04170704e7b@collabora.com>
On Tue, May 28, 2019 at 10:36 AM Guillaume Tucker
<guillaume.tucker@collabora.com> wrote:
> > Can't you mark this as a known issue, to prevent spending cycles on the
> > same bisection, and sending out more bisection reports for the same
> > issue?
>
> Not really, so I've disabled bisections in the linux-gpio tree
> and a few other maintainers' trees for now. I'll see if we can
> come up with a more systematic way of suppressing bisections in
> similar cases (i.e. the issue has been fixed in mainline later
> than the base commit for the branch being tested).
I think this is what the zeroday autobuilder does because
they never seem to show this problem. Thanks for looking
into it!
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-28 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 23:38 linusw/for-next boot bisection: v5.2-rc1-8-g73a790c68d7e on rk3288-veyron-jaq kernelci.org bot
2019-05-28 7:13 ` Guillaume Tucker
2019-05-28 7:45 ` Geert Uytterhoeven
2019-05-28 8:36 ` Guillaume Tucker
2019-05-28 8:41 ` Geert Uytterhoeven
2019-05-28 8:45 ` Linus Walleij [this message]
2019-05-28 13:15 ` Mark Brown
2019-05-28 8:29 ` Linus Walleij
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='CACRpkdb-Dv614V7STLRMpiLkmb_7NVyKnh2oUi=7Rx366tmZ-A@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=broonie@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=geert@linux-m68k.org \
--cc=guillaume.tucker@collabora.com \
--cc=heiko@sntech.de \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=matthew.hart@linaro.org \
--cc=mgalka@collabora.com \
--cc=rui.zhang@intel.com \
--cc=tomeu.vizoso@collabora.com \
--cc=zhangqing@rock-chips.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).