From: Wolfram Sang <wsa@the-dreams.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PULL REQUEST] i2c for 3.13
Date: Fri, 29 Nov 2013 16:17:35 +0100 [thread overview]
Message-ID: <86e2cadbd328a3e40b275cda0349dd50@localhost> (raw)
Linus,
here are some easy but needed fixes for i2c drivers since rc1.
Please pull.
Thanks,
Wolfram
The following changes since commit
6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
Linux 3.13-rc1 (2013-11-22 11:30:55 -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 07a27a0047274e0ba568ce86b6416c34497a99a7:
i2c: bcm2835: Linking platform nodes to adapter nodes (2013-11-28
09:47:53 +0100)
----------------------------------------------------------------
Florian Meier (1):
i2c: bcm2835: Linking platform nodes to adapter nodes
Martin Vogt (1):
i2c: i2c-diolan-u2c: different usb endpoints for DLN-2-U2C
Taras Kondratiuk (1):
i2c: davinci: raw read and write endian fix
Tim Kryger (1):
i2c: i2c-bcm-kona: Fix module build
Victor Kamensky (1):
i2c: omap: raw read and write endian fix
Wei Yongjun (1):
i2c: bcm-kona: remove duplicated include
drivers/i2c/busses/i2c-bcm-kona.c | 3 +--
drivers/i2c/busses/i2c-bcm2835.c | 1 +
drivers/i2c/busses/i2c-davinci.c | 4 ++--
drivers/i2c/busses/i2c-diolan-u2c.c | 16 +++++++++++-----
drivers/i2c/busses/i2c-omap.c | 8 ++++----
5 files changed, 19 insertions(+), 13 deletions(-)
next reply other threads:[~2013-11-29 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 15:17 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-15 12:26 [PULL REQUEST] i2c for 3.13 Wolfram Sang
2013-12-13 8:42 Wolfram Sang
2013-11-18 19:38 Wolfram Sang
2013-11-18 23:46 ` Linus Torvalds
2013-11-19 0:11 ` Rafael J. Wysocki
2013-11-19 15:00 ` Mika Westerberg
2013-11-19 15:56 ` 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=86e2cadbd328a3e40b275cda0349dd50@localhost \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).