From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 1/5] acpi : remove latency_ticks from acpi_processor_cx structure
Date: Thu, 12 Jul 2012 22:47:48 +0200 [thread overview]
Message-ID: <4FFF37F4.3060002@linaro.org> (raw)
In-Reply-To: <201207122234.12851.rjw@sisk.pl>
On 07/12/2012 10:34 PM, Rafael J. Wysocki wrote:
> On Thursday, July 12, 2012, Daniel Lezcano wrote:
>> Remove the latency_ticks field as it is not used.
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>
> Thanks for the patches, but can you please repost them to
> linux-pm@vger.kernel.org so that they are included into the kernel.org
> Patchwork? They will be much easier to review and handle then.
>
> And please CC linux-acpi@vger.kernel.org for all ACPI-related patches in the
> future.
Yes, sure. Sorry for that.
Thanks
-- Daniel
>> ---
>> drivers/acpi/processor_idle.c | 2 --
>> include/acpi/processor.h | 1 -
>> 2 files changed, 0 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
>> index b894627..9ef007d 100644
>> --- a/drivers/acpi/processor_idle.c
>> +++ b/drivers/acpi/processor_idle.c
>> @@ -583,7 +583,6 @@ static void acpi_processor_power_verify_c3(struct acpi_processor *pr,
>> */
>> cx->valid = 1;
>>
>> - cx->latency_ticks = cx->latency;
>> /*
>> * On older chipsets, BM_RLD needs to be set
>> * in order for Bus Master activity to wake the
>> @@ -616,7 +615,6 @@ static int acpi_processor_power_verify(struct acpi_processor *pr)
>> if (!cx->address)
>> break;
>> cx->valid = 1;
>> - cx->latency_ticks = cx->latency; /* Normalize latency */
>> break;
>>
>> case ACPI_STATE_C3:
>> diff --git a/include/acpi/processor.h b/include/acpi/processor.h
>> index ac3bff6..19423c3 100644
>> --- a/include/acpi/processor.h
>> +++ b/include/acpi/processor.h
>> @@ -59,7 +59,6 @@ struct acpi_processor_cx {
>> u8 entry_method;
>> u8 index;
>> u32 latency;
>> - u32 latency_ticks;
>> u32 power;
>> u32 usage;
>> u64 time;
>>
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
--
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
next prev parent reply other threads:[~2012-07-12 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 15:29 [PATCH 1/5] acpi : remove latency_ticks from acpi_processor_cx structure Daniel Lezcano
2012-07-12 15:30 ` [PATCH 2/5] acpi : remove index " Daniel Lezcano
2012-07-12 15:30 ` [PATCH 3/5] acpi : remove usage " Daniel Lezcano
2012-07-12 15:30 ` [PATCH 4/5] acpi : remove power " Daniel Lezcano
2012-07-12 15:30 ` [PATCH 5/5] acpi : remove time " Daniel Lezcano
2012-07-12 20:34 ` [PATCH 1/5] acpi : remove latency_ticks " Rafael J. Wysocki
2012-07-12 20:47 ` Daniel Lezcano [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-12 21:03 Daniel Lezcano
2012-07-12 21:40 ` Rafael J. Wysocki
2012-07-17 20:32 ` Rafael J. Wysocki
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=4FFF37F4.3060002@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.