[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ab700927-d7b6-44c6-bbe0-8c52e4a0f907@linaro.org>
Date: Sat, 13 Apr 2024 10:47:24 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Tudor Ambarus <tudor.ambarus@...aro.org>, peter.griffin@...aro.org
Cc: alim.akhtar@...sung.com, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
andre.draszik@...aro.org, willmcvicker@...gle.com, kernel-team@...roid.com,
s.nawrocki@...sung.com, cw00.choi@...sung.com, mturquette@...libre.com,
sboyd@...nel.org, semen.protsenko@...aro.org, linux-clk@...r.kernel.org,
jaewon02.kim@...sung.com
Subject: Re: [PATCH v3 0/3] clk: samsung: introduce nMUX to reparent MUX
clocks
On 28/03/2024 13:34, Tudor Ambarus wrote:
> v3:
> - update first patch:
> - remove __nMUX() as it duplicated __MUX() with an exception on flags.
> - update commit message
> - update comment and say that nMUX() shall be used where MUX reparenting
> on clock rate chage is allowed
> - collect R-b, A-b tags
>
Sorry for late response, somehow this end up deep in inbox. You
reference some non existing commits, so I think you do not work on
mainline trees.
Also Fixes must come before other patches, so probably first patch
should be squashed with second. Otherwise second patch is not a complete
fix.
Best regards,
Krzysztof
Powered by blists - more mailing lists