From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bjorn Helgaas Subject: [patch 03/54] PNPACPI: continue after _CRS and _PRS errors Date: Fri, 25 Apr 2008 12:38:10 -0600 Message-ID: <20080425183924.705575360@ldl.fc.hp.com> References: <20080425183807.366134771@ldl.fc.hp.com> Return-path: Received: from g1t0027.austin.hp.com ([15.216.28.34]:8178 "EHLO g1t0027.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755268AbYDYSjb (ORCPT ); Fri, 25 Apr 2008 14:39:31 -0400 Content-Disposition: inline; filename=pnpacpi-ignore-errors Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Len Brown Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, Adam Belay , Adam M Belay , Li Shaohua , Matthieu Castet , Thomas Renninger , Rene Herman , Jaroslav Kysela , Andrew Morton Keep going and register the device even if we have trouble parsing _CRS or _PRS. A parsing problem might mean we ignore some resources the device is using, or we might not be able to change its resources. But we should still take note of anything we *could* parse correctly. Also remove reference to dev_id because I plan to remove it soon. Signed-off-by: Bjorn Helgaas Index: work10/drivers/pnp/pnpacpi/core.c =================================================================== --- work10.orig/drivers/pnp/pnpacpi/core.c 2008-04-25 11:12:17.000000000 -0600 +++ work10/drivers/pnp/pnpacpi/core.c 2008-04-25 11:14:44.000000000 -0600 @@ -213,8 +213,7 @@ &dev->res); if (ACPI_FAILURE(status) && (status != AE_NOT_FOUND)) { pnp_err("PnPACPI: METHOD_NAME__CRS failure for %s", - dev_id->id); - goto err1; + acpi_device_hid(device)); } } @@ -223,8 +222,7 @@ dev); if (ACPI_FAILURE(status) && (status != AE_NOT_FOUND)) { pnp_err("PnPACPI: METHOD_NAME__PRS failure for %s", - dev_id->id); - goto err1; + acpi_device_hid(device)); } } @@ -252,8 +250,6 @@ num++; return AE_OK; -err1: - kfree(dev_id); err: kfree(dev); return -EINVAL; --