linux-kernel - Re: [PATCH v2 1/2] clk: Store clk_core for clk_rate

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20221207214840.AFC6AC433D6@smtp.kernel.org>
Date:   Wed, 07 Dec 2022 13:48:38 -0800
From:   Stephen Boyd <sboyd@...nel.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>,
        Michael Turquette <mturquette@...libre.com>,
        Steven Rostedt <rostedt@...dmis.org>, maxime@...no.tech
Cc:     Maxime Ripard <maxime@...no.tech>, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org
Subject: Re: [PATCH v2 1/2] clk: Store clk_core for clk_rate_request

Quoting maxime@...no.tech (2022-10-26 06:46:58)
> The struct clk_rate_request is meant to store the context around a rate
> request such as the parent, boundaries, and so on.
> 
> However, it doesn't store the clock the rate request is submitted to,
> which makes debugging difficult.
> 
> Let's add a pointer to the relevant clk_core instance in order to
> improve the debugging of rate requests in a subsequent patch.
> 
> Signed-off-by: Maxime Ripard <maxime@...no.tech>
> ---

Applied to clk-next