From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-amlogic@lists.infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
linux-next@vger.kernel.org, kernelci-results@groups.io
Subject: Re: next/master bisection: baseline.login on meson-sm1-sei610
Date: Tue, 26 May 2020 22:32:17 +0200 [thread overview]
Message-ID: <CAFBinCC59r-LqSCkVpyjkEr_q+hLQLECDSSiAas+ZF+DoaiJLw@mail.gmail.com> (raw)
In-Reply-To: <ffe2c64c-62ed-9b59-3754-7ede0f0203be@collabora.com>
On Mon, May 25, 2020 at 10:39 AM Guillaume Tucker
<guillaume.tucker@collabora.com> wrote:
>
> Please see the bisection report below about a kernel Oops.
>
> Reports aren't automatically sent to the public while we're
> trialing new bisection features on kernelci.org but this one
> looks valid.
this one is valid indeed and I have sent a fix for it (plus an
unrelated fix): [0]
Also thank you for listening to feedback from a while ago.
This email reminded me to add the Reported-by tag :-)
Martin
[0] https://patchwork.kernel.org/cover/11571203/
prev parent reply other threads:[~2020-05-26 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ec9617c.1c69fb81.b979a.bf47@mx.google.com>
2020-05-25 8:39 ` next/master bisection: baseline.login on meson-sm1-sei610 Guillaume Tucker
2020-05-26 20:32 ` Martin Blumenstingl [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=CAFBinCC59r-LqSCkVpyjkEr_q+hLQLECDSSiAas+ZF+DoaiJLw@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci-results@groups.io \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=narmstrong@baylibre.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).