From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-samsung-soc@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Alim Akhtar <alim.akhtar@samsung.com>
Subject: Re: [PATCH v2] dt-bindings: eeprom/at24: Add samsung,s524ad0xd1 compatible
Date: Mon, 2 May 2022 13:40:34 -0500 [thread overview]
Message-ID: <YnAlomm/0ahEOF5e@robh.at.kernel.org> (raw)
In-Reply-To: <20220426175938.2262966-1-robh@kernel.org>
On Tue, 26 Apr 2022 12:59:39 -0500, Rob Herring wrote:
> The samsung,s524ad0xd1 compatible is in use, but not documented. According
> to arch/arm/mach-s3c/mach-smdk6410.c, the samsung,s524ad0xd1 is compatible
> with the 24c128. As the schema requires a fallback compatible to the
> corresponding Atmel compatible, 'atmel,24c128' is added as a fallback.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> v2:
> - Fix the example in samsung,s3c2410-i2c.yaml
>
> Documentation/devicetree/bindings/eeprom/at24.yaml | 4 +++-
> .../devicetree/bindings/i2c/samsung,s3c2410-i2c.yaml | 2 +-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-02 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 17:59 [PATCH v2] dt-bindings: eeprom/at24: Add samsung, s524ad0xd1 compatible Rob Herring
2022-04-26 18:31 ` [PATCH v2] dt-bindings: eeprom/at24: Add samsung,s524ad0xd1 compatible Krzysztof Kozlowski
2022-05-02 12:02 ` [PATCH v2] dt-bindings: eeprom/at24: Add samsung, s524ad0xd1 compatible Bartosz Golaszewski
2022-05-02 18:40 ` Rob Herring [this message]
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=YnAlomm/0ahEOF5e@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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 \
/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).