From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: devicetree@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
kernelci-results@groups.io,
Andre Przywara <andre.przywara@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: mainline/master bisection: baseline.dmesg.crit on qemu_arm-vexpress-a15
Date: Thu, 16 Jul 2020 09:57:27 +0100 [thread overview]
Message-ID: <b7d63093-a1a8-fbc1-6673-040d6ba8cc8d@collabora.com> (raw)
In-Reply-To: <20200706124951.GA32234@bogus>
On 06/07/2020 13:49, Sudeep Holla wrote:
> Hi,
>
> On Sun, Jul 05, 2020 at 07:12:58PM -0700, kernelci.org bot wrote:
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>> * This automated bisection report was sent to you on the basis *
>> * that you may be involved with the breaking commit it has *
>> * found. No manual investigation has been done to verify it, *
>> * and the root cause of the problem may be somewhere else. *
>> * *
>> * If you do send a fix, please include this trailer: *
>> * Reported-by: "kernelci.org bot" <bot@kernelci.org> *
>> * *
>> * Hope this helps! *
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>
>
> Andre test and replied to one of the similar but earlier reports.
> Unless we get some response to that, we can't proceed and we can't
> do much other than ignoring these reports. Please respond to Andre's
> queries.
Sorry I missed your email, the regression is still there. I'll
reply to André.
Guillaume
_______________________________________________
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:[~2020-07-16 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 2:12 mainline/master bisection: baseline.dmesg.crit on qemu_arm-vexpress-a15 kernelci.org bot
2020-07-06 12:49 ` Sudeep Holla
2020-07-16 8:57 ` Guillaume Tucker [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-16 6:16 kernelci.org bot
2020-07-15 9:35 kernelci.org bot
2020-07-14 11:23 kernelci.org bot
2020-07-08 22:10 kernelci.org bot
2020-07-04 14:20 kernelci.org bot
2020-07-03 14:33 kernelci.org bot
2020-07-03 5:38 kernelci.org bot
2020-07-03 10:49 ` André Przywara
2020-07-16 9:37 ` 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=b7d63093-a1a8-fbc1-6673-040d6ba8cc8d@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.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).