From: Len Brown <lenb@kernel.org>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] acpi: remove dead code
Date: Mon, 18 Oct 2010 12:49:57 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1010181239110.2932@localhost.localdomain> (raw)
In-Reply-To: <20101018084248.23262ba6@nehalam>
On Mon, 18 Oct 2010, Stephen Hemminger wrote:
> Found by running make namespacecheck on linux-next
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
>
> --- a/drivers/acpi/osl.c 2010-10-06 13:42:58.722974685 +0900
...
> /*
> - * Allocate the memory for a spinlock and initialize it.
> - */
> -acpi_status acpi_os_create_lock(acpi_spinlock * handle)
> -{
> - spin_lock_init(*handle);
> -
> - return AE_OK;
> -}
ACPICA declares acpi_os_create_lock in acpiosxf.h,
but never calls it. Bob, can we do away with it?
...
> -int acpi_check_mem_region(resource_size_t start, resource_size_t n,
> - const char *name)
> -{
> - struct resource res = {
> - .start = start,
> - .end = start + n - 1,
> - .name = name,
> - .flags = IORESOURCE_MEM,
> - };
> -
> - return acpi_check_resource_conflict(&res);
> -
> -}
> -EXPORT_SYMBOL(acpi_check_mem_region);
acpi_check_mem_region seems to be entirely
a Linux thing. It is exported to modules -- though
see any that use it.
> --- a/drivers/acpi/processor_driver.c 2010-10-06 13:46:52.594978592 +0900
...
> -EXPORT_SYMBOL(acpi_processor_set_thermal_limit);
...
> --- a/drivers/acpi/processor_thermal.c 2010-10-06 13:47:23.469979232 +0900
...
> -int acpi_processor_set_thermal_limit(acpi_handle handle, int type)
> -{
although acpi_processor_set_thermal_limit() is exported to modules
I don't see any users in recent history.
thanks,
-Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-10-18 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 15:42 [PATCH] acpi: remove dead code Stephen Hemminger
2010-10-18 16:49 ` Len Brown [this message]
2010-10-19 0:42 ` Lin Ming
2010-10-19 4:07 ` Len Brown
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=alpine.LFD.2.00.1010181239110.2932@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=shemminger@vyatta.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