From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@linaro.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] ACPI / processor: Remove unused macros in processor_driver.c
Date: Tue, 25 Jun 2013 00:32:58 +0200 [thread overview]
Message-ID: <4395311.6MOHcFYYSc@vostro.rjw.lan> (raw)
In-Reply-To: <1372059393-15996-1-git-send-email-hanjun.guo@linaro.org>
On Monday, June 24, 2013 03:36:33 PM Hanjun Guo wrote:
> ACPI_PROCESSOR_FILE_INFO, ACPI_PROCESSOR_FILE_THROTTLING and
> ACPI_PROCESSOR_FILE_LIMIT are used for procfs, but this feature was removed
> in commit d09fe555 (ACPI processor: remove deprecated ACPI procfs I/F) long
> ago. So, these macros should also be removed.
>
> ACPI_PROCESSOR_LIMIT_USER and ACPI_PROCESSOR_LIMIT_THERMAL are not used
> by any code, remove them too.
>
> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
Queued up for 3.11.
Thanks,
Rafael
> ---
> drivers/acpi/processor_driver.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/acpi/processor_driver.c b/drivers/acpi/processor_driver.c
> index d93963f..823be116 100644
> --- a/drivers/acpi/processor_driver.c
> +++ b/drivers/acpi/processor_driver.c
> @@ -43,16 +43,10 @@
>
> #define PREFIX "ACPI: "
>
> -#define ACPI_PROCESSOR_FILE_INFO "info"
> -#define ACPI_PROCESSOR_FILE_THROTTLING "throttling"
> -#define ACPI_PROCESSOR_FILE_LIMIT "limit"
> #define ACPI_PROCESSOR_NOTIFY_PERFORMANCE 0x80
> #define ACPI_PROCESSOR_NOTIFY_POWER 0x81
> #define ACPI_PROCESSOR_NOTIFY_THROTTLING 0x82
>
> -#define ACPI_PROCESSOR_LIMIT_USER 0
> -#define ACPI_PROCESSOR_LIMIT_THERMAL 1
> -
> #define _COMPONENT ACPI_PROCESSOR_COMPONENT
> ACPI_MODULE_NAME("processor_driver");
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-06-24 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 7:36 Hanjun Guo
2013-06-24 22:32 ` Rafael J. Wysocki [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=4395311.6MOHcFYYSc@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=hanjun.guo@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.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
all inboxes | Powered by JetHome®