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: <47ddc58b-02d6-42e7-83f8-09bb80d73894@kernel.org>
Date: Sat, 30 Aug 2025 11:18:14 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Denzeel Oliva <wachiturroxd150@...il.com>,
 Sylwester Nawrocki <s.nawrocki@...sung.com>,
 Chanwoo Choi <cw00.choi@...sung.com>, Alim Akhtar <alim.akhtar@...sung.com>,
 Michael Turquette <mturquette@...libre.com>, Stephen Boyd
 <sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>
Cc: linux-samsung-soc@...r.kernel.org, linux-clk@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 devicetree@...r.kernel.org
Subject: Re: [PATCH v4 3/4] clk: samsung: exynos990: update CLK_NR_TOP for new
 IDs clocks

On 25/08/2025 07:51, Denzeel Oliva wrote:
> The new clock IDs have been added and put last,
> it is necessary to change.
> 
> Signed-off-by: Denzeel Oliva <wachiturroxd150@...il.com>
> ---
>  drivers/clk/samsung/clk-exynos990.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/samsung/clk-exynos990.c b/drivers/clk/samsung/clk-exynos990.c
> index 105ba0363..9fcdad7cc 100644
> --- a/drivers/clk/samsung/clk-exynos990.c
> +++ b/drivers/clk/samsung/clk-exynos990.c
> @@ -17,7 +17,7 @@
>  #include "clk-pll.h"
>  
>  /* NOTE: Must be equal to the last clock ID increased by one */
> -#define CLKS_NR_TOP (CLK_GOUT_CMU_VRA_BUS + 1)
> +#define CLKS_NR_TOP (CLK_DOUT_CMU_CLK_CMUREF + 1)

This belongs to the driver patch introducing these new clocks. Such
change alone makes no sense or commit msg really does not explain issue
being fixed here.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ