From: Krzysztof Kozlowski <krzk@kernel.org>
To: Faraz Ata <faraz.ata@samsung.com>,
andi.shyti@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, alim.akhtar@samsung.com
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
rosa.pila@samsung.com, dev.tailor@samsung.com
Subject: Re: [RESEND PATCH 1/2] dt-bindings: i2c: exynos5: add exynosautov920-hsi2c compatible
Date: Thu, 9 Oct 2025 19:13:14 +0900 [thread overview]
Message-ID: <4a03bec1-34e2-444e-acb8-cae72dcbe6c2@kernel.org> (raw)
In-Reply-To: <20251009101911.2802433-1-faraz.ata@samsung.com>
On 09/10/2025 19:19, Faraz Ata wrote:
> Add "samsung,exynosautov920-hsi2c" dedicated compatible for
> HSI2C found in ExynosAutov920 SoC.
>
> Signed-off-by: Faraz Ata <faraz.ata@samsung.com>
> ---
> Note: This patch was previously sent separately. Resending now as part of a
> two-patch series to avoid dt-binding check error. No functional changes from the earlier submission[1]
It's not necessary. You only need to provide lore link to bindings in
patch changelog. Read carefully report you received.
Also, do not resend non-fix patches during merge window. It's just noise.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-09 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251009101023epcas5p2de61d08e2d4a180bbcf2f2708d267336@epcas5p2.samsung.com>
2025-10-09 10:19 ` [RESEND PATCH 1/2] dt-bindings: i2c: exynos5: add exynosautov920-hsi2c compatible Faraz Ata
2025-10-09 10:13 ` Krzysztof Kozlowski [this message]
2025-10-10 4:55 ` Faraz Ata
[not found] ` <CGME20251009101027epcas5p249214ced403b82c4fb7085006901504b@epcas5p2.samsung.com>
2025-10-09 10:19 ` [RESEND PATCH 2/2] arm64: dts: exynosautov920: Add DT node for all I2C ports Faraz Ata
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=4a03bec1-34e2-444e-acb8-cae72dcbe6c2@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dev.tailor@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=faraz.ata@samsung.com \
--cc=krzk+dt@kernel.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=robh@kernel.org \
--cc=rosa.pila@samsung.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).