From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: "Saravana Kannan" <skannan@codeaurora.org>,
박경민 <kyungmin.park@samsung.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] PM / devfreq: Rewrite devfreq_update_status() to fix multiple bugs
Date: Tue, 04 Mar 2014 10:06:17 +0000 (GMT) [thread overview]
Message-ID: <8984550.302431393927576253.JavaMail.weblogic@epv6ml05> (raw)
> 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.
Cheers,
MyungJoo
next reply other threads:[~2014-03-04 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 10:06 MyungJoo Ham [this message]
2014-03-04 20:25 ` [PATCH] PM / devfreq: Rewrite devfreq_update_status() to fix multiple bugs Saravana Kannan
-- strict thread matches above, loose matches on Subject: below --
2014-02-28 3:38 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=8984550.302431393927576253.JavaMail.weblogic@epv6ml05 \
--to=myungjoo.ham@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=skannan@codeaurora.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).