[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPcyv4jTe48rqGvLBXOH4tLtYM5q6JX1dF7EBApnD291+NaUgg@mail.gmail.com>
Date: Tue, 15 Feb 2022 09:28:42 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Paul Menzel <pmenzel@...gen.mpg.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Linux ACPI <linux-acpi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>, regressions@...ts.linux.dev
Subject: Re: New warning: ACPI: CEDT not present
On Tue, Feb 15, 2022 at 9:14 AM Rafael J. Wysocki <rafael@...nel.org> wrote:
>
> On Tue, Feb 15, 2022 at 5:22 PM Dan Williams <dan.j.williams@...el.com> wrote:
> >
> > On Mon, Feb 14, 2022 at 11:52 PM Paul Menzel <pmenzel@...gen.mpg.de> wrote:
> > >
> > > #regzbot introduced: 2d03e46a4bad20191d07b83ec1242d5f002577be
> > >
> > > Dear Dan,
> > >
> > >
> > > On the Dell Latitude E7250, Linux 5.17-rc3 logs the warning below
> > > (`dmesg --level=warn`):
> > >
> > > ACPI: CEDT not present
> > >
> > > I think commit 2d03e46a4bad (ACPI: Add a context argument for table
> > > parsing handlers), part of Linux since 5.17-rc1, is the reason.
> > >
> > > If I understand it correctly, CEDT is not to be expected on older
> > > devices, so the warning is not justified. Can something be done about it?
> >
> > Rafael,
> >
> > I'm inclined to just delete the warning altogether, but special casing
> > is also an option. Any preference?
>
> Change it into pr_debug()?
Sounds good, patch inbound.
Powered by blists - more mailing lists