From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Dominik Bartenstein <dom-K271P2BsTd0@public.gmane.org>
Cc: ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: WARN: please read if you applyied 00_thinkpad_workaround.diff (Re: IBM Thinkpad A31 | News)
Date: Sat, 18 Jan 2003 18:08:44 +0100 [thread overview]
Message-ID: <20030118170844.GE12516@poup.poupinou.org> (raw)
In-Reply-To: <20030118164525.GD12516-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
On Sat, Jan 18, 2003 at 05:45:25PM +0100, Ducrot Bruno wrote:
Hi Dom,
> > >
> > > Cheers,
> >
>
> Here is then.
>
> This patch is against acpi-20030109. It override the
..
Ouch. Just realize that the portion:
> +acpi_status
> +acpi_os_table_override(struct acpi_table_header * existing_table,
> + struct acpi_table_header ** new_table)
> +{
> + if (!existing_table || !new_table)
> + return AE_BAD_PARAMETER;
> +
> + if (!memcmp(existing_table->signature, "ECDT", 4)) {
> + struct acpi_table_ecdt *old = (struct acpi_table_ecdt *) existing_table;
> + struct acpi_table_ecdt **new = (struct acpi_table_ecdt **) new_table;
> +
> + if (!memcmp(old->header.oem_id, "IBM", 3))
> + return (verify_ibm_ecdt(old, new));
> + }
> + return AE_OK;
> +}
That can let *new_table to be not NULL if we do not enter
the if statement.
It should be:
acpi_status
acpi_os_table_override(struct acpi_table_header * existing_table,
struct acpi_table_header ** new_table)
{
if (!existing_table || !new_table)
return AE_BAD_PARAMETER;
*new_table = NULL;
if (!memcmp(existing_table->signature, "ECDT", 4)) {
struct acpi_table_ecdt *old = (struct acpi_table_ecdt *) existing_table;
struct acpi_table_ecdt **new = (struct acpi_table_ecdt **) new_table;
if (!memcmp(old->header.oem_id, "IBM", 3))
return (verify_ibm_ecdt(old, new));
}
return AE_OK;
}
Or else you will have a kernel oops at acpi init stage.
Cheers,
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
next prev parent reply other threads:[~2003-01-18 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 18:47 IBM Thinkpad A31 | News Dominik Bartenstein
[not found] ` <200301172111.15037.dom@wahuu.at>
[not found] ` <20030117210321.GC12516@poup.poupinou.org>
[not found] ` <200301172204.52963.dom@wahuu.at>
[not found] ` <200301172204.52963.dom-K271P2BsTd0@public.gmane.org>
2003-01-18 16:45 ` Ducrot Bruno
[not found] ` <20030118164525.GD12516-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-01-18 17:08 ` Ducrot Bruno [this message]
[not found] ` <20030118170844.GE12516-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-01-20 13:42 ` WARN: please read if you applyied 00_thinkpad_workaround.diff (Re: IBM Thinkpad A31 | News) x545
[not found] ` <200301201442.27358.x545-hi6Y0CQ0nG0@public.gmane.org>
2003-01-20 14:09 ` thinkpad workaround v2 Ducrot Bruno
[not found] ` <20030120140926.GA11487-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-01-20 14:30 ` Dominik Bartenstein
[not found] ` <20030120144413.GD11487@poup.poupinou.org>
[not found] ` <200301201554.13984.dom@wahuu.at>
[not found] ` <200301201554.13984.dom-K271P2BsTd0@public.gmane.org>
2003-01-20 15:40 ` Ducrot Bruno
[not found] ` <20030120154043.GI11487-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-01-20 17:15 ` apologizes (was Re: Re: thinkpad workaround v2.) Ducrot Bruno
2003-01-20 15:17 ` thinkpad workaround v2 x545
[not found] ` <200301171947.54174.dom-K271P2BsTd0@public.gmane.org>
2003-01-21 7:25 ` IBM Thinkpad A31 | News Christian Zoz
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=20030118170844.GE12516@poup.poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=dom-K271P2BsTd0@public.gmane.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