diff options
author | Nishanth Menon <nm@ti.com> | 2012-05-18 12:26:19 -0500 |
---|---|---|
committer | Kevin Hilman <khilman@ti.com> | 2012-06-19 15:23:29 -0700 |
commit | b110547e586eb5825bc1d04aa9147bff83b57672 (patch) | |
tree | 6547f2dea4af3251a647e391a3eeac65f54ecdd3 /Documentation/cgroups/resource_counter.txt | |
parent | 164e0cbf608214bddc4d28e2777f49e7b3a0f65c (diff) |
ARM: OMAP2+: OPP: Fix to ensure check of right oppdef after bad one
Commit 9fa2df6b90786301b175e264f5fa9846aba81a65
(ARM: OMAP2+: OPP: allow OPP enumeration to continue if device is not present)
makes the logic:
for (i = 0; i < opp_def_size; i++) {
<snip>
if (!oh || !oh->od) {
<snip>
continue;
}
<snip>
opp_def++;
}
In short, the moment we hit a "Bad OPP", we end up looping the list
comparing against the bad opp definition pointer for the rest of the
iteration count. Instead, increment opp_def in the for loop itself
and allow continue to be used in code without much thought so that
we check the next set of OPP definition pointers :)
Cc: Steve Sakoman <steve@sakoman.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: stable@vger.kernel.org
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
Diffstat (limited to 'Documentation/cgroups/resource_counter.txt')
0 files changed, 0 insertions, 0 deletions