From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PULL REQUEST] i2c for 3.12
Date: Sat, 28 Sep 2013 16:37:35 +0200 [thread overview]
Message-ID: <20130928143729.GA8755@katana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
Linus,
here are some driver bugfixes for the I2C subsystem. Please pull.
Thanks,
Wolfram
The following changes since commit 4a10c2ac2f368583138b774ca41fac4207911983:
Linux 3.12-rc2 (2013-09-23 15:41:09 -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 bf4169100c909667ede6af67668b3ecce6928343:
i2c: ismt: initialize DMA buffer (2013-09-28 16:32:12 +0200)
----------------------------------------------------------------
Chew, Chiau Ee (1):
i2c: designware: 10-bit addressing mode enabling if I2C_DYNAMIC_TAR_UPDATE is set
James Ralston (1):
i2c: ismt: initialize DMA buffer
Kim Phillips (1):
i2c: s3c2410: fix clk_disable/clk_unprepare WARNings
Thierry Reding (2):
i2c: mv64xxx: Fix some build warnings
i2c: mv64xxx: Do not use writel_relaxed()
drivers/i2c/busses/i2c-designware-core.c | 26 ++++++++++++++++++++------
drivers/i2c/busses/i2c-ismt.c | 3 +++
drivers/i2c/busses/i2c-mv64xxx.c | 16 +++++++++-------
drivers/i2c/busses/i2c-s3c2410.c | 2 --
4 files changed, 32 insertions(+), 15 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-09-28 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 14:37 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-12 6:20 [PULL REQUEST] i2c for 3.12 Wolfram Sang
2013-09-05 9:03 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=20130928143729.GA8755@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@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).