From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [GIT PULL] at24: updates for v5.17
Date: Mon, 3 Jan 2022 11:57:49 +0100 [thread overview]
Message-ID: <20220103105749.85404-1-brgl@bgdev.pl> (raw)
Hi Wolfram,
Here are the updates for the next merge window for the at24 EEPROM driver.
Details are in the signed tag, please pull.
Best Regards,
Bartosz Golaszewski
The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/at24-updates-for-v5.17
for you to fetch changes up to d08aea21c89dc2d302cadb5c2cc5410b6c3395c8:
eeprom: at24: Add support for 24c1025 EEPROM (2021-12-13 14:42:39 +0100)
----------------------------------------------------------------
at24 updates for v5.17
- add support for a new model: Microchip 24c1025
- reorganize the compatible definitions in the DT binding document
- drop the at24_client structure by retrieving the struct device associated
with the chip's regmap
----------------------------------------------------------------
Geert Uytterhoeven (1):
dt-bindings: at24: Rework special case compatible handling
Heiner Kallweit (1):
eeprom: at24: remove struct at24_client
Maxim Kochetkov (2):
dt-bindings: at24: add at24c1025
eeprom: at24: Add support for 24c1025 EEPROM
Documentation/devicetree/bindings/eeprom/at24.yaml | 29 ++++-----
drivers/misc/eeprom/at24.c | 68 ++++++++++------------
2 files changed, 47 insertions(+), 50 deletions(-)
next reply other threads:[~2022-01-03 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 10:57 Bartosz Golaszewski [this message]
2022-01-06 13:35 ` [GIT PULL] at24: updates for v5.17 Wolfram Sang
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=20220103105749.85404-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).