From: Mark Brown <broonie@kernel.org>
To: Will Deacon <will.deacon@arm.com>
Cc: catalin.marinas@arm.com, John Garry <john.garry@huawei.com>,
linux-arm-kernel@lists.infradead.org,
Wei Xu <xuwei5@hisilicon.com>,
kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 175 boots: 18 failed, 143 passed with 10 offline, 1 untried/unknown, 3 conflicts (next-20181211)
Date: Tue, 11 Dec 2018 16:48:57 +0000 [thread overview]
Message-ID: <20181211164857.GM6686@sirena.org.uk> (raw)
In-Reply-To: <20181211163558.GB12597@edgewater-inn.cambridge.arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 654 bytes --]
On Tue, Dec 11, 2018 at 04:35:59PM +0000, Will Deacon wrote:
> On Tue, Dec 11, 2018 at 03:23:11PM +0000, Mark Brown wrote:
> > Unfortunately it looks like the bug has actually been around for a while
> > but wasn't stopping us getting to a prompt:
> > https://storage.kernelci.org/next/master/next-20181210/arm64/defconfig/lab-collabora/boot-hip07-d05.html
> > and it might still be some unrelated hang there.
> The "bad commit" is just updating the -next metadata, so the bisection
> doesn't appear to be useful :(
Sorry, that's the commit to start a bisection on rather than the result
of a bisection (ie, what you'd pass to "git bisect bad").
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-12-11 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5c0fb738.1c69fb81.f62ad.3f45@mx.google.com>
2018-12-11 15:23 ` next/master boot: 175 boots: 18 failed, 143 passed with 10 offline, 1 untried/unknown, 3 conflicts (next-20181211) Mark Brown
2018-12-11 16:24 ` John Garry
2018-12-11 16:50 ` Mark Brown
2018-12-11 17:23 ` Guillaume Tucker
2018-12-11 20:15 ` Wei Xu
2018-12-13 16:16 ` John Garry
2018-12-11 16:35 ` Will Deacon
2018-12-11 16:48 ` Mark Brown [this message]
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=20181211164857.GM6686@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=john.garry@huawei.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.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).