From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: "André Draszik" <andre.draszik@linaro.org>,
"Peter Griffin" <peter.griffin@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>
Cc: Will McVicker <willmcvicker@google.com>,
Sam Protsenko <semen.protsenko@linaro.org>,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] arm64: dts: exynos: gs101: specify empty clocks for remaining pinctrl
Date: Thu, 2 May 2024 07:51:39 +0100 [thread overview]
Message-ID: <498ff366-b247-4586-b02e-5cbfba5927ac@linaro.org> (raw)
In-Reply-To: <20240430-samsung-pinctrl-busclock-dts-v2-4-14fc988139dd@linaro.org>
All 4 patches could have been squashed in a single patch as they do the
same thing, but I'm fine either way:
Reviewed-by: Tudor Ambarus <tudor.ambarus@linaro.org>
next prev parent reply other threads:[~2024-05-02 6:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 9:49 [PATCH v2 0/4] hook up pin controller clocks on Google Tensor gs101 André Draszik
2024-04-30 9:49 ` [PATCH v2 1/4] arm64: dts: exynos: gs101: specify bus clock for pinctrl (far) alive André Draszik
2024-05-02 6:49 ` Tudor Ambarus
2024-04-30 9:49 ` [PATCH v2 2/4] arm64: dts: exynos: gs101: specify bus clock for pinctrl_peric[01] André Draszik
2024-05-02 6:49 ` Tudor Ambarus
2024-04-30 9:49 ` [PATCH v2 3/4] arm64: dts: exynos: gs101: specify bus clock for pinctrl_hsi2 André Draszik
2024-05-02 6:50 ` Tudor Ambarus
2024-04-30 9:49 ` [PATCH v2 4/4] arm64: dts: exynos: gs101: specify empty clocks for remaining pinctrl André Draszik
2024-05-02 6:51 ` Tudor Ambarus [this message]
2024-05-02 10:44 ` André Draszik
2024-05-03 8:36 ` Krzysztof Kozlowski
2024-05-03 8:37 ` [PATCH v2 0/4] hook up pin controller clocks on Google Tensor gs101 Krzysztof Kozlowski
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=498ff366-b247-4586-b02e-5cbfba5927ac@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=semen.protsenko@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
all inboxes | Powered by JetHome®