[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <88719b92-1d69-4571-9323-a844ffc90d7e@linaro.org>
Date: Wed, 27 Dec 2023 12:40:31 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Varada Pavani <v.pavani@...sung.com>, mturquette@...libre.com,
sboyd@...nel.org, krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, s.nawrocki@...sung.com, tomasz.figa@...il.com
Cc: linux-samsung-soc@...r.kernel.org, alim.akhtar@...sung.com,
aswani.reddy@...sung.com, pankaj.dubey@...sung.com
Subject: Re: [PATCH 2/2] clk: samsung: Fix typo error and extra space
On 26/12/2023 18:05, Varada Pavani wrote:
>> hardware
>> - * registers to acheive a fast co-oridinated rate change for all the
>> CPU domain
>> + * registers to achieve a fast co-oridinated rate change for all the
>> + CPU domain
>> * clocks.
>> *
>> * On a rate change request for the CPU clock, the rate change is
>> propagated @@ -181,7 +181,7 @@ static int exynos_cpuclk_pre_rate_change(struct clk_notifier_data *ndata,
>> * If the old parent clock speed is less than the clock speed of
>> * the alternate parent, then it should be ensured that at no point
>> * the armclk speed is more than the old_prate until the dividers are
>> - * set. Also workaround the issue of the dividers being set to lower
>> + * set. Also workaround the issue of the dividers being set to lower
>
> Why? The double-space is correct.
>
> Okay, I couldn’t see any double space at the end of the statement apart from this line and below one. So updated to have uniformity.
Wait, there are only two statements here, so where do you expect double
space? There is no "one space at the end of the statement".
Your quoting is still not correct. Which part of above is quote of my
message, which yours?
Best regards,
Krzysztof
Powered by blists - more mailing lists