Linux-i2c Archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] at24: fixes for v6.9-rc6
Date: Thu, 25 Apr 2024 13:58:47 +0200	[thread overview]
Message-ID: <20240425115847.18359-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Wolfram,

Please pull the following set of fixes for the next RC.

Thanks,
Bartosz

The following changes since commit 4cece764965020c22cff7665b18a012006359095:

  Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/at24-fixes-for-v6.9-rc6

for you to fetch changes up to f42c97027fb75776e2e9358d16bf4a99aeb04cf2:

  eeprom: at24: fix memory corruption race condition (2024-04-23 10:07:48 +0200)

----------------------------------------------------------------
at24 fixes for v6.9-rc6

- move the nvmem registration after the test one-byte read to improve the
  situation with a race condition in nvmem
- fix the DT schema for ST M24C64-D

----------------------------------------------------------------
Daniel Okazaki (1):
      eeprom: at24: fix memory corruption race condition

Rob Herring (1):
      dt-bindings: eeprom: at24: Fix ST M24C64-D compatible schema

 Documentation/devicetree/bindings/eeprom/at24.yaml |  5 +----
 drivers/misc/eeprom/at24.c                         | 18 +++++++++---------
 2 files changed, 10 insertions(+), 13 deletions(-)

             reply	other threads:[~2024-04-25 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 11:58 Bartosz Golaszewski [this message]
2024-04-26  6:00 ` [GIT PULL] at24: fixes for v6.9-rc6 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=20240425115847.18359-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=bartosz.golaszewski@linaro.org \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).