From: Krzysztof Kozlowski <krzk@kernel.org>
To: Igor Belwon <igor.belwon@mentallysanemainliners.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Tomasz Figa <tomasz.figa@gmail.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/5] dt-bindings: pinctrl: samsung: add exynos990-wakeup-eint compatible
Date: Wed, 16 Oct 2024 09:20:30 +0200 [thread overview]
Message-ID: <7dc638fe-2bee-4693-9bca-2732eb502724@kernel.org> (raw)
In-Reply-To: <20241015210450.964093-3-igor.belwon@mentallysanemainliners.org>
On 15/10/2024 23:04, Igor Belwon wrote:
> Add a dedicated compatible for the exynos990-wakeup-eint node.
This we see from the diff. Explain the hardware, why suddenly it became
compatible with exynos850, even though it was not.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-16 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 21:04 [PATCH v2 0/5] Add Exynos990 pinctrl and chipid drivers Igor Belwon
2024-10-15 21:04 ` [PATCH v2 1/5] dt-bindings: pinctrl: samsung: Add exynos990-pinctrl compatible Igor Belwon
2024-10-15 21:04 ` [PATCH v2 2/5] dt-bindings: pinctrl: samsung: add exynos990-wakeup-eint compatible Igor Belwon
2024-10-16 7:20 ` Krzysztof Kozlowski [this message]
2024-10-15 21:04 ` [PATCH v2 3/5] pinctrl: samsung: Add Exynos 990 SoC pinctrl configuration Igor Belwon
2024-10-15 21:04 ` [PATCH v2 4/5] arm64: dts: exynos: Add Exynos 990 pinctrl nodes Igor Belwon
2024-10-15 21:04 ` [PATCH v2 5/5] arm64: dts: exynos: Add button support for c1s Igor Belwon
2024-10-16 7:04 ` Krzysztof Kozlowski
2024-10-15 22:03 ` [PATCH v2 0/5] Add Exynos990 pinctrl and chipid drivers Linus Walleij
2024-10-16 7:06 ` Krzysztof Kozlowski
2024-10-16 7:19 ` Krzysztof Kozlowski
2024-10-16 14:41 ` Igor Belwon
2024-10-16 14:49 ` 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=7dc638fe-2bee-4693-9bca-2732eb502724@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=igor.belwon@mentallysanemainliners.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=tomasz.figa@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
all inboxes | Powered by JetHome®