From: Krzysztof Kozlowski <krzk@kernel.org>
To: aidenisik@member.fsf.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Aiden Isik <aidenisik+git@member.fsf.org>
Subject: Re: [PATCH 1/2] dt-bindings: hwinfo: samsung,exynos-chipid: Add exynos5515 compatible
Date: Mon, 17 Aug 2026 13:10:13 +0200 [thread overview]
Message-ID: <d592c554-5e43-48f8-a1bf-5dc6c6525c27@kernel.org> (raw)
In-Reply-To: <20260817-for-next-lucky7-chipid-v1-1-eb2908705c0d@member.fsf.org>
On 17/08/2026 12:11, Aiden Isik via B4 Relay wrote:
> From: Aiden Isik <aidenisik@member.fsf.org>
>
> Add "samsung,exynos5515-chipid" compatible string to binding document.
> Use the "samsung,exynos850-chipid" compatible, as it is the same on that
> SoC as exynos5515.
I do not see how you use "samsung,exynos850-chipid", probably you meant
that devices are compatible? Just say that you add Exynos5515 ChipID
fully compatible with foo bar (no differences in registers) instead of
repeating the diff.
s/exynos5515/Exynos5515/, in every commit msg
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-17 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 10:11 [PATCH 0/2] Hi there, Aiden Isik via B4 Relay
2026-08-17 10:11 ` [PATCH 1/2] dt-bindings: hwinfo: samsung,exynos-chipid: Add exynos5515 compatible Aiden Isik via B4 Relay
2026-08-17 10:16 ` sashiko-bot
2026-08-17 11:05 ` Aiden Isik
2026-08-17 11:10 ` Krzysztof Kozlowski [this message]
2026-08-17 10:11 ` [PATCH 2/2] soc: samsung: exynos-chipid: Add exynos5515 SoC support Aiden Isik via B4 Relay
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=d592c554-5e43-48f8-a1bf-5dc6c6525c27@kernel.org \
--to=krzk@kernel.org \
--cc=aidenisik+git@member.fsf.org \
--cc=aidenisik@member.fsf.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.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 \
/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