From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: peter.griffin@linaro.org, Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: s.nawrocki@samsung.com, cw00.choi@samsung.com,
alim.akhtar@samsung.com, mturquette@baylibre.com,
sboyd@kernel.org, semen.protsenko@linaro.org,
andre.draszik@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, willmcvicker@google.com,
kernel-team@android.com
Subject: Re: [PATCH v4 0/2] clk: samsung: introduce nMUX to reparent MUX clocks
Date: Mon, 22 Apr 2024 09:20:22 +0200 [thread overview]
Message-ID: <171377042206.10231.3797208490823201633.b4-ty@linaro.org> (raw)
In-Reply-To: <20240419100915.2168573-1-tudor.ambarus@linaro.org>
On Fri, 19 Apr 2024 10:09:13 +0000, Tudor Ambarus wrote:
> v4:
> - squash nMUX patch with the PERIC0 patch so that it becomes a single
> entity fixing the introduction of the PERIC0 clocks. PERIC1 fix comes
> after, as the PERIC1 clocks were introduced after PERIC0.
> - fix the fixes tag of the PERIC1 patch.
>
> 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
>
> [...]
Applied, thanks!
[1/2] clk: samsung: gs101: propagate PERIC0 USI SPI clock rate
https://git.kernel.org/krzk/linux/c/7b54d9113cd4923432c0b2441c5e2663873b4e5b
[2/2] clk: samsung: gs101: propagate PERIC1 USI SPI clock rate
https://git.kernel.org/krzk/linux/c/7cf0324ba0bc61a8c360d23d284e06d2994b1fef
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
prev parent reply other threads:[~2024-04-22 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 10:09 [PATCH v4 0/2] clk: samsung: introduce nMUX to reparent MUX clocks Tudor Ambarus
2024-04-19 10:09 ` [PATCH v4 1/2] clk: samsung: gs101: propagate PERIC0 USI SPI clock rate Tudor Ambarus
2024-04-19 10:09 ` [PATCH v4 2/2] clk: samsung: gs101: propagate PERIC1 " Tudor Ambarus
2024-04-22 7:20 ` Krzysztof Kozlowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171377042206.10231.3797208490823201633.b4-ty@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.griffin@linaro.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).