From: Len Brown <len.brown@intel.com>
To: akpm@osdl.org
Cc: linux-acpi@vger.kernel.org, rdunlap@xenotime.net, greg@kroah.com
Subject: Re: [patch 05/14] acpi: handle firmware_register init errors
Date: Tue, 15 Aug 2006 23:26:41 -0400 [thread overview]
Message-ID: <200608152326.42299.len.brown@intel.com> (raw)
In-Reply-To: <200608150537.k7F5bOTW011542@shell0.pdx.osdl.net>
Applied.
Looking forward to removing this call to firmware_register() completely soon.
thanks,
-Len
On Tuesday 15 August 2006 01:37, akpm@osdl.org wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Check and handle init errors.
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> Cc: Greg KH <greg@kroah.com>
> Cc: "Brown, Len" <len.brown@intel.com>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> drivers/acpi/bus.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff -puN drivers/acpi/bus.c~acpi-handle-firmware_register-init-errors drivers/acpi/bus.c
> --- a/drivers/acpi/bus.c~acpi-handle-firmware_register-init-errors
> +++ a/drivers/acpi/bus.c
> @@ -25,6 +25,7 @@
> #include <linux/module.h>
> #include <linux/init.h>
> #include <linux/ioport.h>
> +#include <linux/kernel.h>
> #include <linux/list.h>
> #include <linux/sched.h>
> #include <linux/pm.h>
> @@ -738,7 +739,10 @@ static int __init acpi_init(void)
> return -ENODEV;
> }
>
> - firmware_register(&acpi_subsys);
> + result = firmware_register(&acpi_subsys);
> + if (result < 0)
> + printk(KERN_WARNING "%s: firmware_register error: %d\n",
> + __FUNCTION__, result);
>
> result = acpi_bus_init();
>
> _
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2006-08-16 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 5:37 [patch 05/14] acpi: handle firmware_register init errors akpm
2006-08-16 3:26 ` Len Brown [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=200608152326.42299.len.brown@intel.com \
--to=len.brown@intel.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.