From: Al Stone <ahs3@redhat.com>
To: Timur Tabi <timur@codeaurora.org>, Al Stone <al.stone@linaro.org>
Cc: linux-acpi@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linaro-kernel@lists.linaro.org, linux-ia64@vger.kernel.org,
patches@linaro.org, linux-pm@vger.kernel.org,
linaro-acpi@lists.linaro.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
lkml <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v2 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro
Date: Wed, 26 Aug 2015 14:30:25 -0600 [thread overview]
Message-ID: <55DE21E1.6070700@redhat.com> (raw)
In-Reply-To: <CAOZdJXXCnb7ChYqh-QYptTQBmfESDPaauThHyu8Dav6Qs_+4Bw@mail.gmail.com>
On 08/26/2015 09:38 AM, Timur Tabi wrote:
> On Wed, Aug 19, 2015 at 5:07 PM, Al Stone <al.stone@linaro.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@redhat.com
-----------------------------------
next prev parent reply other threads:[~2015-08-26 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 22:07 [PATCH v2 0/5] ACPI: Provide better MADT subtable sanity checks Al Stone
2015-08-19 22:07 ` [PATCH v2 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro Al Stone
2015-08-26 15:38 ` Timur Tabi
2015-08-26 20:30 ` Al Stone [this message]
2015-09-07 15:32 ` Sudeep Holla
2015-09-08 23:00 ` Al Stone
2015-09-09 19:57 ` Al Stone
2015-09-10 16:20 ` Sudeep Holla
2015-09-10 20:43 ` Al Stone
2015-09-11 8:49 ` Sudeep Holla
2015-08-19 22:07 ` [PATCH v2 2/5] ACPI / ARM64: remove usage of BAD_MADT_ENTRY/BAD_MADT_GICC_ENTRY Al Stone
2015-08-20 10:13 ` Will Deacon
2015-08-20 16:57 ` Al Stone
2015-08-24 10:04 ` Will Deacon
2015-08-19 22:07 ` [PATCH v2 3/5] ACPI / IA64: remove usage of BAD_MADT_ENTRY Al Stone
2015-08-19 22:07 ` [PATCH v2 4/5] ACPI / X86: " Al Stone
2015-08-19 22:07 ` [PATCH v2 5/5] ACPI: remove definition of BAD_MADT_ENTRY macro Al Stone
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=55DE21E1.6070700@redhat.com \
--to=ahs3@redhat.com \
--cc=al.stone@linaro.org \
--cc=lenb@kernel.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=timur@codeaurora.org \
/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).