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 3.18
Date: Sat, 6 Dec 2014 09:26:34 +0100 [thread overview]
Message-ID: <20141206082629.GA2311@katana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Linus,
here are two more driver bugfixes for I2C which would be good to have in
3.18. This branch is based on your tree from two days ago to make sure
the fixes I sent previously were already included.
Please pull and thanks,
Wolfram
The following changes since commit 7cc78f8fa02c2485104b86434acbc1538a3bd807:
context_tracking: Restore previous state in schedule_user (2014-12-03 20:55:58 -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 681d15a0f527af7ab3a783e1037de86fbcb136ac:
i2c: cadence: Set the hardware time-out register to maximum value (2014-12-04 19:25:41 +0100)
----------------------------------------------------------------
Grygorii Strashko (1):
i2c: davinci: generate STP always when NACK is received
Vishnu Motghare (1):
i2c: cadence: Set the hardware time-out register to maximum value
drivers/i2c/busses/i2c-cadence.c | 11 +++++++++++
drivers/i2c/busses/i2c-davinci.c | 8 +++-----
2 files changed, 14 insertions(+), 5 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-12-06 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 8:26 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-03 20:22 [PULL REQUEST] i2c for 3.18 Wolfram Sang
2014-11-08 17:16 Wolfram Sang
2014-10-18 13:54 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=20141206082629.GA2311@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).