From: "Rob Herring (Arm)" <robh@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
~postmarketos/upstreaming@lists.sr.ht, linux-i2c@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: eeprom: at24: Add compatible for Giantec GT24P64A
Date: Thu, 11 Dec 2025 10:55:45 -0600 [thread overview]
Message-ID: <176547214530.1553950.16205619497487516656.robh@kernel.org> (raw)
In-Reply-To: <20251210-fp4-cam-prep-v1-1-0eacbff271ec@fairphone.com>
On Wed, 10 Dec 2025 10:05:27 +0900, Luca Weiss wrote:
> Add the compatible for another 64Kb EEPROM from Giantec.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
> Documentation/devicetree/bindings/eeprom/at24.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-12-11 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 1:05 [PATCH 0/4] Preparations for camera support on Fairphone 4 Luca Weiss
2025-12-10 1:05 ` [PATCH 1/4] dt-bindings: eeprom: at24: Add compatible for Giantec GT24P64A Luca Weiss
2025-12-11 16:55 ` Rob Herring (Arm) [this message]
2025-12-10 1:05 ` [PATCH 2/4] arm64: dts: qcom: sm7225-fairphone-fp4: Add camera EEPROMs Luca Weiss
2025-12-16 12:10 ` Konrad Dybcio
2025-12-10 1:05 ` [PATCH 3/4] arm64: dts: qcom: sm7225-fairphone-fp4: Add camera fixed regulators Luca Weiss
2025-12-16 12:48 ` Bryan O'Donoghue
2025-12-16 13:51 ` Konrad Dybcio
2025-12-10 1:05 ` [PATCH 4/4] arm64: dts: qcom: sm7225-fairphone-fp4: Enable CCI pull-up Luca Weiss
2025-12-16 12:10 ` Konrad Dybcio
2025-12-17 9:22 ` (subset) [PATCH 0/4] Preparations for camera support on Fairphone 4 Bartosz Golaszewski
2026-01-05 14:07 ` Bjorn Andersson
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=176547214530.1553950.16205619497487516656.robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®