From: Shawn Guo <shawnguo@kernel.org>
To: Raag Jadav <raagjadav@gmail.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, Li Yang <leoyang.li@nxp.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] arm64: dts: ls1046a: fix eeprom entries
Date: Mon, 9 Aug 2021 15:46:23 +0800 [thread overview]
Message-ID: <20210809074623.GN30984@dragon> (raw)
In-Reply-To: <1628105086-8172-2-git-send-email-raagjadav@gmail.com>
On Thu, Aug 05, 2021 at 12:54:45AM +0530, Raag Jadav wrote:
> ls1046afrwy and ls1046ardb boards have CAT24C04[1] and CAT24C05[2]
> eeproms respectively. Both are 4Kb (512 bytes) in size,
> and compatible with AT24C04[3].
> Remove multi-address entries, as both the boards have a single chip each.
>
> [1] https://www.onsemi.com/pdf/datasheet/cat24c01-d.pdf
> [2] https://www.onsemi.com/pdf/datasheet/cat24c03-d.pdf
> [3] https://ww1.microchip.com/downloads/en/DeviceDoc/doc0180.pdf
>
> Signed-off-by: Raag Jadav <raagjadav@gmail.com>
Applied, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Raag Jadav <raagjadav@gmail.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, Li Yang <leoyang.li@nxp.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] arm64: dts: ls1046a: fix eeprom entries
Date: Mon, 9 Aug 2021 15:46:23 +0800 [thread overview]
Message-ID: <20210809074623.GN30984@dragon> (raw)
In-Reply-To: <1628105086-8172-2-git-send-email-raagjadav@gmail.com>
On Thu, Aug 05, 2021 at 12:54:45AM +0530, Raag Jadav wrote:
> ls1046afrwy and ls1046ardb boards have CAT24C04[1] and CAT24C05[2]
> eeproms respectively. Both are 4Kb (512 bytes) in size,
> and compatible with AT24C04[3].
> Remove multi-address entries, as both the boards have a single chip each.
>
> [1] https://www.onsemi.com/pdf/datasheet/cat24c01-d.pdf
> [2] https://www.onsemi.com/pdf/datasheet/cat24c03-d.pdf
> [3] https://ww1.microchip.com/downloads/en/DeviceDoc/doc0180.pdf
>
> Signed-off-by: Raag Jadav <raagjadav@gmail.com>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-09 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 19:24 [PATCH v2 0/2] fix eeprom entries for ls1046afrwy and ls1046ardb Raag Jadav
2021-08-04 19:24 ` Raag Jadav
2021-08-04 19:24 ` [PATCH v2 1/2] arm64: dts: ls1046a: fix eeprom entries Raag Jadav
2021-08-04 19:24 ` Raag Jadav
2021-08-06 23:46 ` Li Yang
2021-08-06 23:46 ` Li Yang
2021-08-09 7:46 ` Shawn Guo [this message]
2021-08-09 7:46 ` Shawn Guo
2021-08-04 19:24 ` [PATCH v2 2/2] dt-bindings: at24: add ON Semi CAT24C04 and CAT24C05 Raag Jadav
2021-08-04 19:24 ` Raag Jadav
2021-08-05 19:08 ` Bartosz Golaszewski
2021-08-05 19:08 ` Bartosz Golaszewski
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=20210809074623.GN30984@dragon \
--to=shawnguo@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raagjadav@gmail.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.