From: Wolfram Sang <wsa@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Rosin <peda@axentia.se>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PULL REQUEST] i2c for 5.10
Date: Sat, 12 Dec 2020 19:30:46 +0100 [thread overview]
Message-ID: <20201212183046.GA8096@kunai> (raw)
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
Linus,
the AT24 EEPROM driver still needs a bugfix for 5.10.
Please pull.
Thanks,
Wolfram
The following changes since commit 0477e92881850d44910a7e94fc2c46f96faa131f:
Linux 5.10-rc7 (2020-12-06 14:25:12 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current
for you to fetch changes up to e977aaf899a6d3b3d6658da66e262b6e307ae3a2:
Merge tag 'at24-fixes-for-v5.10' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux into i2c/for-current (2020-12-11 23:23:30 +0100)
----------------------------------------------------------------
Diego Santa Cruz (1):
misc: eeprom: at24: fix NVMEM name with custom AT24 device name
Wolfram Sang (1):
Merge tag 'at24-fixes-for-v5.10' of git://git.kernel.org/.../brgl/linux into i2c/for-current
drivers/misc/eeprom/at24.c | 1 -
1 file changed, 1 deletion(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-12-12 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 18:30 Wolfram Sang [this message]
2020-12-12 21:03 ` [PULL REQUEST] i2c for 5.10 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-12-05 22:11 Wolfram Sang
2020-12-05 23:33 ` pr-tracker-bot
2020-11-07 18:39 Wolfram Sang
2020-11-07 19:43 ` pr-tracker-bot
2020-10-25 12:37 Wolfram Sang
2020-10-25 18:35 ` pr-tracker-bot
2020-10-21 6:55 Wolfram Sang
2020-10-21 18:35 ` pr-tracker-bot
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=20201212183046.GA8096@kunai \
--to=wsa@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=torvalds@linux-foundation.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 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).