linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: skannan@codeaurora.org (Saravana Kannan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PM / devfreq: Rewrite devfreq_update_status() to fix multiple bugs
Date: Tue, 04 Mar 2014 12:25:24 -0800	[thread overview]
Message-ID: <531636B4.1060202@codeaurora.org> (raw)
In-Reply-To: <8984550.302431393927576253.JavaMail.weblogic@epv6ml05>

On 03/04/2014 02:06 AM, MyungJoo Ham wrote:
>> The current devfreq_update_status() has the following bugs:
>> - If previous frequency doesn't have a valid level, it does an out of bounds
>>    access into the trans_table and causes memory corruption.
>> - When the new frequency doesn't have a valid level, the time spent in the
>>    new frequency is counted towards the next valid frequency switch instead of
>>    being ignored.
>> - The time spent on the previous frequency is added to the new frequency's
>>    stats instead of the previous frequency's stats.
>>
>> This patch fixes all of this.
>>
>> Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
> 
> Merged.
> 
> It appears to be Greg's LTS material as well.
> 

Thanks!

-Saravana

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation

       reply	other threads:[~2014-03-04 20:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8984550.302431393927576253.JavaMail.weblogic@epv6ml05>
2014-03-04 20:25 ` Saravana Kannan [this message]
2014-02-28  3:38 [PATCH] PM / devfreq: Rewrite devfreq_update_status() to fix multiple bugs Saravana Kannan
2014-03-04  0:35 ` Saravana Kannan

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=531636B4.1060202@codeaurora.org \
    --to=skannan@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).