[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55DE21E1.6070700@redhat.com>
Date: Wed, 26 Aug 2015 14:30:25 -0600
From: Al Stone <ahs3@...hat.com>
To: Timur Tabi <timur@...eaurora.org>, Al Stone <al.stone@...aro.org>
Cc: linux-acpi@...r.kernel.org,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linaro-kernel@...ts.linaro.org, linux-ia64@...r.kernel.org,
patches@...aro.org, linux-pm@...r.kernel.org,
linaro-acpi@...ts.linaro.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
lkml <linux-kernel@...r.kernel.org>, Len Brown <lenb@...nel.org>
Subject: Re: [PATCH v2 1/5] ACPI: add in a bad_madt_entry() function to
eventually replace the macro
On 08/26/2015 09:38 AM, Timur Tabi wrote:
> On Wed, Aug 19, 2015 at 5:07 PM, Al Stone <al.stone@...aro.org> wrote:
>> + pr_err("Variable length MADT subtable %d is wrong size: %d\n",
>> + entry->type, entry->length);
>> + return 1;
>> + }
>> + }
>> + } else {
>> + if (entry->length != len) {
>> + pr_err("MADT subtable %d is wrong size: %d\n",
>> + len, entry->type);
>
> Can we make these a little more descriptive?
>
> pr_err("Variable length MADT subtable type %d is wrong size: %d,
> should be %d\n",
> entry->type, entry->length, len);
>
> pr_err("MADT subtable type %d is wrong size: %d, should be %d\n",
> entry->type, entry->length, len);
>
Sure. It's always a fine line between verbose and not enough info.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@...hat.com
-----------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists