linux-kernel - Re: [PATCH] clk: Fix best_parent_rate after moving code into a separate function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9b4ca44aeaa784946f5e25e7ec23954f.sboyd@kernel.org>
Date:   Tue, 13 Jun 2023 12:00:07 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Marek Szyprowski <m.szyprowski@...sung.com>,
        Maxime Ripard <mripard@...nel.org>,
        Michael Turquette <mturquette@...libre.com>
Cc:     Marek Szyprowski <m.szyprowski@...sung.com>,
        linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clk: Fix best_parent_rate after moving code into a separate function

Quoting Marek Szyprowski (2023-06-13 06:16:31)
> best_parent_rate entry is still being used in the code and needs to be
> always updated regardless of the CLK_SET_RATE_NO_REPARENT flag.
> 
> Fixes: 1b4e99fda73f ("clk: Move no reparent case into a separate function")
> Signed-off-by: Marek Szyprowski <m.szyprowski@...sung.com>
> ---

Applied to clk-next