[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181119183613.GB26707@localhost.localdomain>
Date: Mon, 19 Nov 2018 11:36:13 -0700
From: Keith Busch <keith.busch@...el.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dave Hansen <dave.hansen@...el.com>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH 6/7] acpi: Create subtable parsing infrastructure
On Mon, Nov 19, 2018 at 10:58:12AM +0100, Rafael J. Wysocki wrote:
> > +static unsigned long __init
> > +acpi_get_entry_length(struct acpi_subtable_entry *entry)
> > +{
> > + switch (entry->type) {
> > + case ACPI_SUBTABLE_COMMON:
> > + return entry->hdr->common.length;
> > + }
> > + WARN_ONCE(1, "invalid acpi type\n");
>
> AFAICS this does a WARN_ONCE() on information obtained from firmware.
>
> That is not a kernel problem, so generating traces in that case is not
> a good idea IMO. Moreover, users can't really do much about this in
> the majority of cases, so a pr_info() message should be sufficient.
Sure thing, I'll fix that up for the next revision.
Powered by blists - more mailing lists