From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PULL REQUEST] i2c for 4.2
Date: Mon, 3 Aug 2015 22:47:14 +0200 [thread overview]
Message-ID: <20150803204711.GA2749@katana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
Linus,
this pull request from I2C was planned for the last rc, yet for holiday
reasons I sadly couldn't send it out that weekend. I hope it is still
okay for the next rc. Inside is a refcounting bugfix for the i2c-core,
bugfixes for the generic bus recovery algorithm and for its omap-user,
making binary file attributes for EEPROMs behave POSIX compliant, and a
small typo fix while we are here. Please pull!
Thanks,
Wolfram
The following changes since commit bc0195aad0daa2ad5b0d76cce22b167bc3435590:
Linux 4.2-rc2 (2015-07-12 15:10:30 -0700)
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 e3311469734093724b10c2a81c1193197db03b78:
i2c: fix leaked device refcount on of_find_i2c_* error path (2015-08-01 12:11:58 +0200)
----------------------------------------------------------------
Jan Luebbe (2):
i2c: core: only use set_scl for bus recovery after calling prepare_recovery
i2c: omap: fix bus recovery setup
Masanari Iida (1):
i2c: Fix typo in i2c-bfin-twi.c
Vladimir Zapolskiy (3):
i2c: slave eeprom: clean up sysfs bin attribute read()/write()
misc: eeprom: at24: clean up at24_bin_write()
i2c: fix leaked device refcount on of_find_i2c_* error path
drivers/i2c/busses/i2c-bfin-twi.c | 4 ++--
drivers/i2c/busses/i2c-omap.c | 11 +++++++++++
drivers/i2c/i2c-core.c | 24 +++++++++++++++++-------
drivers/i2c/i2c-slave-eeprom.c | 6 ------
drivers/misc/eeprom/at24.c | 3 ---
5 files changed, 30 insertions(+), 18 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-08-03 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 20:47 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-11 10:06 [PULL REQUEST] i2c for 4.2 Wolfram Sang
2015-06-25 18:51 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=20150803204711.GA2749@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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).