From: Krzysztof Kozlowski <krzk@kernel.org>
To: Denzeel Oliva <wachiturroxd150@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Sam Protsenko <semen.protsenko@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, linux-i2c@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2 0/8] arm64: dts: exynos990: Add PERIC0/1 USI, UART and HSI2C support
Date: Mon, 8 Sep 2025 08:46:33 +0200 [thread overview]
Message-ID: <3e815b1f-57dc-4c6a-aa73-fb5ab77e7cd7@kernel.org> (raw)
In-Reply-To: <20250907-perics-add-usinodes-v2-0-58f41796d2d3@gmail.com>
On 08/09/2025 00:13, Denzeel Oliva wrote:
> Hi,
>
> This series adds device tree support for PERIC0/1 blocks:
>
> - Add sysreg nodes required for peripheral configuration
> - Add USI, UART and HSI2C controller nodes
> - Update bindings with Exynos990 compatibles
>
> These changes enable serial communication interfaces
> (I2C, UART) for Exynos990 SoC.
>
> Changes in v2:
> - Remove unnecessary blank lines in HSI2C nodes.
One patchset per 24h, allow people to actually review your code.
>
> Denzeel Oliva
>
> Signed-off-by: Denzeel Oliva <wachiturroxd150@gmail.com>
> ---
> Denzeel Oliva (8):
> dt-bindings: soc: samsung: exynos-sysreg: Add Exynos990 PERIC0/1 compatibles
> arm64: dts: exynos990: Add sysreg nodes for PERIC0 and PERIC1
> dt-bindings: soc: samsung: Add Exynos990 USI compatible
> arm64: dts: exynos990: Add USI nodes for PERIC0 and PERIC1
> dt-bindings: serial: samsung: Add Exynos990 UART compatible
> arm64: dts: exynos990: Add UART nodes for PERIC0/1
> dt-bindings: i2c: exynos5: Add exynos990-hsi2c compatible
I don't get why you keep sending this in multiple patchsets now. It was
on the list prviously, but now no versioning and it starts from v1. How
maintainers can understand this?
Anyway, I went through my queue this weekend and this was probably last
time I will apply something, maybe except next revision of GS101 ACPM
clocks. This means this patchset will wait for next merge window.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-09-08 6:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 22:13 [PATCH v2 0/8] arm64: dts: exynos990: Add PERIC0/1 USI, UART and HSI2C support Denzeel Oliva
2025-09-07 22:13 ` [PATCH v2 1/8] dt-bindings: soc: samsung: exynos-sysreg: Add Exynos990 PERIC0/1 compatibles Denzeel Oliva
2025-09-07 22:13 ` [PATCH v2 2/8] arm64: dts: exynos990: Add sysreg nodes for PERIC0 and PERIC1 Denzeel Oliva
2025-09-07 22:13 ` [PATCH v2 3/8] dt-bindings: soc: samsung: Add Exynos990 USI compatible Denzeel Oliva
2025-09-07 22:13 ` [PATCH v2 4/8] arm64: dts: exynos990: Add USI nodes for PERIC0 and PERIC1 Denzeel Oliva
2025-09-07 22:13 ` [PATCH v2 5/8] dt-bindings: serial: samsung: Add Exynos990 UART compatible Denzeel Oliva
2025-09-09 7:18 ` Krzysztof Kozlowski
2025-09-07 22:13 ` [PATCH v2 6/8] arm64: dts: exynos990: Add UART nodes for PERIC0/1 Denzeel Oliva
2025-09-09 18:24 ` kernel test robot
2025-09-07 22:13 ` [PATCH v2 7/8] dt-bindings: i2c: exynos5: Add exynos990-hsi2c compatible Denzeel Oliva
2025-09-12 22:02 ` Wolfram Sang
2025-09-07 22:13 ` [PATCH v2 8/8] arm64: dts: exynos990: Add HSI2C nodes for PERIC0/1 Denzeel Oliva
2025-09-08 6:46 ` 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=3e815b1f-57dc-4c6a-aa73-fb5ab77e7cd7@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=wachiturroxd150@gmail.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 NNTP newsgroup(s).