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 4.15
Date: Thu, 30 Nov 2017 12:12:22 +0100 [thread overview]
Message-ID: <20171130111222.11887-1-brgl@bgdev.pl> (raw)
Wolfram,
please consider pulling the following fixes for v4.15. While it doesn't
fix any regression introduced in the v4.15 merge window, we have a
feature in at24 since linux v4.8 - reading the mac address block from
at24mac series - which turned out to be not working.
This pull request contains changes that fix it together with a patch
that hardens the read and write argument sanitization with
out-of-bounds checks that were missing.
----------------------------------------------------------------
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/at24-4.15-fixes-for-wolfram
for you to fetch changes up to d9bcd462daf34aebb8de9ad7f76de0198bb5a0f0:
eeprom: at24: check at24_read/write arguments (2017-11-29 16:05:37 +0100)
----------------------------------------------------------------
AT24 fixes for v4.15
----------------------------------------------------------------
Bartosz Golaszewski (1):
eeprom: at24: correctly set the size for at24mac402
Heiner Kallweit (2):
eeprom: at24: fix reading from 24MAC402/24MAC602
eeprom: at24: check at24_read/write arguments
drivers/misc/eeprom/at24.c | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
next reply other threads:[~2017-11-30 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 11:12 Bartosz Golaszewski [this message]
2017-12-02 22:40 ` [GIT PULL] at24 fixes for 4.15 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=20171130111222.11887-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 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.