From: Christoph Hellwig <hch@lst.de>
To: Mark Brown <broonie@kernel.org>
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>, Christoph Hellwig <hch@lst.de>,
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 17:40:53 +0200 [thread overview]
Message-ID: <20190905154053.GA21701@lst.de> (raw)
In-Reply-To: <20190905153938.GB4053@sirena.co.uk>
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?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mark Brown <broonie@kernel.org>
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>, Christoph Hellwig <hch@lst.de>,
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 17:40:53 +0200 [thread overview]
Message-ID: <20190905154053.GA21701@lst.de> (raw)
In-Reply-To: <20190905153938.GB4053@sirena.co.uk>
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?
_______________________________________________
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:40 UTC|newest]
Thread overview: 12+ 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 0:15 ` Kevin Hilman
2019-09-05 15:39 ` Mark Brown
2019-09-05 15:40 ` Christoph Hellwig [this message]
2019-09-05 15:40 ` Christoph Hellwig
2019-09-05 15:43 ` Mark Brown
2019-09-05 17:02 ` Catalin Marinas
2019-09-05 17:02 ` Catalin Marinas
2019-09-05 19:43 ` Kevin Hilman
2019-09-05 19:43 ` Kevin Hilman
2019-09-04 19:05 kernelci.org bot
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=20190905154053.GA21701@lst.de \
--to=hch@lst.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--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 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.