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@xxxxxxxxxx>
>
> Thanks for the patches, but can you please repost them to
> linux-pm@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
