From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Al Stone <ahs3@redhat.com>
Cc: Al Stone <al.stone@linaro.org>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
linux-pm@vger.kernel.org, linaro-acpi@lists.linaro.org,
linaro-kernel@lists.linaro.org, patches@linaro.org,
"lenb@kernel.org" <lenb@kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"fenghua.yu@intel.com" <fenghua.yu@intel.com>,
Pavel Machek <pavel@ucw.cz>,
"tglx@linutronix.de" <tglx@linutronix.de>,
mingo@redhat.com, "H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks
Date: Thu, 17 Sep 2015 00:34:26 +0000 [thread overview]
Message-ID: <2360913.mWVNIccye0@vostro.rjw.lan> (raw)
In-Reply-To: <55F9988D.5080002@redhat.com>
On Wednesday, September 16, 2015 10:27:57 AM Al Stone wrote:
> On 09/16/2015 10:24 AM, Al Stone wrote:
> > On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote:
> >> On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote:
> >>> On 09/09/2015 03:09 PM, Al Stone wrote:
> >>>> Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity
> >>>> check on the various subtables that are defined for the MADT. The check
> >>>> compares the size of the subtable data structure as defined by ACPICA to
> >>>> the length entry in the subtable. If they are not the same, the assumption
> >>>> is that the subtable is incorrect.
> >>>>
>
> [snip...]
>
> >> I'm going to apply this series if people have no problems with it. I do think
> >> it is slightly overkill, but then as long as it works ...
> >>
> >> Thanks,
> >> Rafael
> >>
>
> Would you prefer I send out the updated version with Sudeep's fix to apply
> instead of this version?
Yes, I would.
> Or have you picked that up already?
No, I haven't.
> Easily updated and sent out, if it'll make your life simpler....
Yes, please.
Thanks,
Rafael
prev parent reply other threads:[~2015-09-17 0:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 21:09 [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks Al Stone
2015-09-09 21:09 ` [PATCH v3 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro Al Stone
2015-09-10 12:14 ` [Linaro-acpi] [PATCH v3 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the Graeme Gregory
2015-09-10 14:13 ` Al Stone
2015-09-09 21:09 ` [PATCH v3 2/5] ACPI / ARM64: remove usage of BAD_MADT_ENTRY/BAD_MADT_GICC_ENTRY Al Stone
2015-09-09 21:09 ` [PATCH v3 3/5] ACPI / IA64: remove usage of BAD_MADT_ENTRY Al Stone
2015-09-09 21:09 ` [PATCH v3 4/5] ACPI / X86: " Al Stone
2015-09-09 21:09 ` [PATCH v3 5/5] ACPI: remove definition of BAD_MADT_ENTRY macro Al Stone
2015-09-10 12:16 ` [Linaro-acpi] [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks Graeme Gregory
2015-09-15 21:13 ` Al Stone
2015-09-16 2:44 ` Rafael J. Wysocki
2015-09-16 16:24 ` Al Stone
2015-09-16 16:27 ` Al Stone
2015-09-16 19:26 ` Al Stone
2015-09-17 0:34 ` Rafael J. Wysocki [this message]
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=2360913.mWVNIccye0@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=ahs3@redhat.com \
--cc=al.stone@linaro.org \
--cc=fenghua.yu@intel.com \
--cc=hpa@linux.intel.com \
--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=mingo@redhat.com \
--cc=patches@linaro.org \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
/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