From: "Guillaume Tucker" <guillaume.tucker@collabora.com>
To: Hans de Goede <hdegoede@redhat.com>, Mark Brown <broonie@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-pci@vger.kernel.org,
"kernelci@groups.io" <kernelci@groups.io>,
"kernelci-results@groups.io" <kernelci-results@groups.io>
Subject: Re: next/master bisection: baseline.login on asus-C523NA-A20057-coral
Date: Mon, 4 Apr 2022 20:48:17 +0100 [thread overview]
Message-ID: <73a7cc3c-9d51-3e44-a4e4-cd116ffccc92@collabora.com> (raw)
In-Reply-To: <16E2C910B4947F17.5433@groups.io>
On 04/04/2022 20:44, Guillaume Tucker wrote:
> Well the issue seems to have been fixed on mainline
Sorry, I meant linux-next. It is also booting on mainline but I
don't think the regression ever went further than linux-next:
https://linux.kernelci.org/test/plan/id/6246654e60a1cb470cae0680/
Guillaume
next prev parent reply other threads:[~2022-04-04 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <623c13ec.1c69fb81.8cbdb.5a7a@mx.google.com>
[not found] ` <Yjyv03JsetIsTJxN@sirena.org.uk>
[not found] ` <4e9fca2f-0af1-3684-6c97-4c35befd5019@redhat.com>
[not found] ` <Yjzua8Wye/3DHBKx@sirena.org.uk>
[not found] ` <f8e96f8a-c19c-6acd-2f54-688924f491e8@redhat.com>
[not found] ` <28699579-8384-ff3b-5662-fb56d8ced766@collabora.com>
2022-04-04 19:44 ` next/master bisection: baseline.login on asus-C523NA-A20057-coral Guillaume Tucker
2022-04-05 8:13 ` Hans de Goede
2022-04-05 17:57 ` Bjorn Helgaas
[not found] ` <16E2C910B4947F17.5433@groups.io>
2022-04-04 19:48 ` Guillaume Tucker [this message]
[not found] <20220405235315.GA101393@bhelgaas>
[not found] ` <20220406185931.GA165754@bhelgaas>
[not found] ` <Yk3r9uhIHmNumtxi@sirena.org.uk>
2022-04-06 20:11 ` Guillaume Tucker
2022-04-07 15:17 ` Denys Fedoryshchenko
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=73a7cc3c-9d51-3e44-a4e4-cd116ffccc92@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=hdegoede@redhat.com \
--cc=kernelci-results@groups.io \
--cc=kernelci@groups.io \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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