From: "Rob Herring (Arm)" <robh@kernel.org>
To: Danila Tikhonov <danila@jiaxyga.com>
Cc: conor+dt@kernel.org, ~postmarketos/upstreaming@lists.sr.ht,
linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, andersson@kernel.org,
linux-kernel@vger.kernel.org, konradybcio@kernel.org,
krzk+dt@kernel.org, brgl@bgdev.pl, linux@mainlining.org
Subject: Re: [PATCH 3/4] dt-bindings: eeprom: at24: Add compatible for Giantec GT24P128E
Date: Mon, 3 Feb 2025 16:59:36 -0600 [thread overview]
Message-ID: <173862357520.500395.299611236712032118.robh@kernel.org> (raw)
In-Reply-To: <20250203111429.22062-4-danila@jiaxyga.com>
On Mon, 03 Feb 2025 14:14:28 +0300, Danila Tikhonov wrote:
> Add the compatible for another 128Kb EEPROM from Giantec.
>
> Signed-off-by: Danila Tikhonov <danila@jiaxyga.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-02-03 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 11:14 [PATCH 0/4] sm7325-nothing-spacewar: Preparing for the cameras Danila Tikhonov
2025-02-03 11:14 ` [PATCH 1/4] arm64: dts: qcom: sm7325-nothing-spacewar: Add CAM fixed-regulators Danila Tikhonov
2025-02-03 11:14 ` [PATCH 2/4] dt-bindings: eeprom: at24: Add compatible for Puya P24C64F Danila Tikhonov
2025-02-03 22:59 ` Rob Herring (Arm)
2025-02-03 11:14 ` [PATCH 3/4] dt-bindings: eeprom: at24: Add compatible for Giantec GT24P128E Danila Tikhonov
2025-02-03 22:59 ` Rob Herring (Arm) [this message]
2025-02-03 11:14 ` [PATCH 4/4] arm64: dts: qcom: sm7325-nothing-spacewar: Enable camera EEPROMs Danila Tikhonov
2025-02-05 8:59 ` (subset) [PATCH 0/4] sm7325-nothing-spacewar: Preparing for the cameras Bartosz Golaszewski
2025-02-26 13:40 ` 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=173862357520.500395.299611236712032118.robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=danila@jiaxyga.com \
--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=linux@mainlining.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®