From: Mark Brown <broonie@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Steven Liu <steven.liu@mediatek.com>,
kernel-build-reports@lists.linaro.org,
Kevin Hilman <khilman@baylibre.com>,
linux-mediatek@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: next/master boot: 310 boots: 11 failed, 292 passed with 6 offline, 1 untried/unknown (next-20190904)
Date: Thu, 5 Sep 2019 16:43:55 +0100 [thread overview]
Message-ID: <20190905154355.GC4053@sirena.co.uk> (raw)
In-Reply-To: <20190905154053.GA21701@lst.de>
[-- Attachment #1.1: Type: text/plain, Size: 590 bytes --]
On Thu, Sep 05, 2019 at 05:40:53PM +0200, Christoph Hellwig wrote:
> On Thu, Sep 05, 2019 at 04:39:38PM +0100, Mark Brown wrote:
> > On Wed, Sep 04, 2019 at 05:15:53PM -0700, Kevin Hilman wrote:
> > > [ + Steven Liu who donated this board to my kernelCI lab ]
> > Also adding Christoph since this was bisected to his commit and Catalin
> > and Will since this was an architecture change.
> Given Will in CC the problem is on arm64?
Yes, this is an arm64 system. It seems to be the only one in KernelCI
that's been affected so it's not like the entire architecture exploded
or anything.
[-- 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
next prev parent reply other threads:[~2019-09-05 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d700b15.1c69fb81.2abcd.479b@mx.google.com>
2019-09-04 19:27 ` next/master boot: 310 boots: 11 failed, 292 passed with 6 offline, 1 untried/unknown (next-20190904) Mark Brown
2019-09-05 0:15 ` Kevin Hilman
2019-09-05 15:39 ` Mark Brown
2019-09-05 15:40 ` Christoph Hellwig
2019-09-05 15:43 ` Mark Brown [this message]
2019-09-05 17:02 ` Catalin Marinas
2019-09-05 19:43 ` Kevin Hilman
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=20190905154355.GC4053@sirena.co.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=hch@lst.de \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=steven.liu@mediatek.com \
--cc=will@kernel.org \
/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).