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: fixes for v5.14
Date: Mon, 5 Jul 2021 11:33:14 +0200 [thread overview]
Message-ID: <20210705093314.20322-1-brgl@bgdev.pl> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=a, Size: 1101 bytes --]
Wolfram,
Please pull the following fix for an issue that was raised recently on the
list. If multiple eeproms would have the same labels in the system, the driver
would refuse to bind any other than the first one.
Best Regards,
Bartosz Golaszewski
The following changes since commit 62fb9874f5da54fdb243003b386128037319b219:
Linux 5.13 (2021-06-27 15:21:11 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/at24-fixes-for-v5.14
for you to fetch changes up to c36748ac545421d94a5091c754414c0f3664bf10:
misc: eeprom: at24: Always append device id even if label property is set. (2021-07-01 18:49:37 +0200)
----------------------------------------------------------------
at24 fixes for v5.14
- fix a problem with repeating labels not getting a device id
----------------------------------------------------------------
Jérôme Glisse (1):
misc: eeprom: at24: Always append device id even if label property is set.
drivers/misc/eeprom/at24.c | 17 +++++++----------
1 file changed, 7 insertions(+), 10 deletions(-)
next reply other threads:[~2021-07-05 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 9:33 Bartosz Golaszewski [this message]
2021-07-18 12:51 ` [GIT PULL] at24: fixes for v5.14 Bartosz Golaszewski
2021-07-20 20:30 ` 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=20210705093314.20322-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).