From: matthieu castet <castet.matthieu@free.fr>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: [Patch] PnPacpi parser fix
Date: Sun, 21 Nov 2004 20:27:00 +0100 [thread overview]
Message-ID: <41A0EC04.6070100@free.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 196 bytes --]
Hi,
this patch fix a bug in the pnpacpi parser : the pnpacpi parser supposed
that are no resource after EndDependentFn.
Please apply.
Signed-Off-By: Matthieu Castet <castet.matthieu@free.fr>
[-- Attachment #2: pnpacpi_parser.patch --]
[-- Type: text/x-patch, Size: 1127 bytes --]
--- linux-2.6.9/drivers/pnp/pnpacpi/rsparser.c.old 2004-11-12 22:55:10.000000000 +0100
+++ linux-2.6.9/drivers/pnp/pnpacpi/rsparser.c 2004-11-20 10:44:36.000000000 +0100
@@ -443,6 +443,7 @@
struct acpipnp_parse_option_s {
struct pnp_option *option;
+ struct pnp_option *independent_option;
struct pnp_dev *dev;
};
@@ -506,7 +507,15 @@
parse_data->option = option;
break;
case ACPI_RSTYPE_END_DPF:
- return AE_CTRL_TERMINATE;
+ /*only one EndDependentFn is allowed*/
+ if (!parse_data->independent_option) {
+ pnp_warn("PnPACPI: more than one EndDependentFn");
+ return AE_ERROR;
+ }
+ parse_data->option = parse_data->independent_option;
+ parse_data->independent_option = NULL;
+ break;
default:
pnp_warn("PnPACPI:Option type: %d not handle", res->id);
return AE_ERROR;
@@ -524,6 +533,7 @@
parse_data.option = pnp_register_independent_option(dev);
if (!parse_data.option)
return AE_ERROR;
+ parse_data.independent_option = parse_data.option;
parse_data.dev = dev;
status = acpi_walk_resources(handle, METHOD_NAME__PRS,
pnpacpi_option_resource, &parse_data);
next reply other threads:[~2004-11-21 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 19:27 matthieu castet [this message]
[not found] <4203AFC5.8070308@free.fr>
2005-02-05 9:07 ` [PATCH] PNPACPI " matthieu castet
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=41A0EC04.6070100@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome