From: "Pierre Asselin" <pa@panix.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Pierre Asselin" <pa@panix.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Linux ACPI" <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"\"Uwe Kleine-König\"" <u.kleine-koenig@pengutronix.de>,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Subject: Re: [PATCH v1] ACPI: bus: Rework system-level device notification handling
Date: Mon, 27 Mar 2023 09:33:37 -0400 [thread overview]
Message-ID: <bd57500b3900e5cce3f1a65de59959bc.squirrel@mail.panix.com> (raw)
In-Reply-To: <CAJZ5v0gAyGNAT-t=pQ9wEbNAqzixEfm5dKZuRJVv-YQ=1=LbFw@mail.gmail.com>
> On Fri, Mar 24, 2023 at 4:54 PM Pierre Asselin <pa@panix.com> wrote:
>>
>> Rafael, the patch is good for 6.3-rc1 (boots to early userspace).
>> I'll try a full install now.
>
> I'm wondering if this has succeeded?
Yes. I've been running 6.3-rc1 + Rafael's patch for a few days now
and all is well.
(Okay, the simple framebuffer has psychedelic color effects but that too
has a workaround. One bug at a time.)
Are these emails getting through ? I see them on patchwork but not
on linux-acpi or regressions.
--PA
next prev parent reply other threads:[~2023-03-27 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 13:33 [PATCH v1] ACPI: bus: Rework system-level device notification handling Rafael J. Wysocki
2023-03-24 15:13 ` Pierre Asselin
2023-03-24 15:19 ` Pierre Asselin
2023-03-24 15:25 ` Pierre Asselin
2023-03-24 15:54 ` Pierre Asselin
2023-03-27 11:44 ` Rafael J. Wysocki
2023-03-27 13:33 ` Pierre Asselin [this message]
2023-03-27 14:41 ` Rafael J. Wysocki
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=bd57500b3900e5cce3f1a65de59959bc.squirrel@mail.panix.com \
--to=pa@panix.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=regressions@leemhuis.info \
--cc=rjw@rjwysocki.net \
--cc=u.kleine-koenig@pengutronix.de \
/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).