From: Ben Dooks <ben@trinity.fluff.org>
To: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: [PULL] Pull request for bjdooks' for-linus/i2c-2636 tree
Date: Sat, 14 Aug 2010 16:09:18 +0100 [thread overview]
Message-ID: <20100814150918.GA29606@ben-laptop.fluff.org> (raw)
Please pull the following tree:
The following changes since commit 45d7f32c7a43cbb9592886d38190e379e2eb2226:
Linus Torvalds (1):
Merge git://git.kernel.org/.../cmetcalf/linux-tile
are available in the git repository at:
git://git.fluff.org/bjdooks/linux.git for-linus/i2c-2636
Ben Dooks (4):
Merge branch 'davinci-i2c' of git://git.kernel.org/.../khilman/linux-davinci into for-2636/i2c/davinci
Merge branch 'for-2636/i2c/pxa' into next-i2c
Merge branch 'for-2636/i2c/nxp' into next-i2c
Merge branch 'for-2636/i2c/nuc' into next-i2c
Chaithrika U S (4):
i2c: davinci: misc. cleanups: remove MOD_REG_BIT and IO_ADDRESS usage
i2c: davinci: Add helper functions for power management
i2c: davinci: Add suspend/resume support
i2c: davinci: Add cpufreq support
Dirk Behme (1):
i2c: davinci: Fix smbus Oops with AIC33 usage
Kevin Wells (1):
i2c: Enable NXP LPC support in Kconfig
Marc Kleine-Budde (1):
i2c-pxa: fix compiler warning, due to missing const
Philby John (1):
i2c: davinci: bus recovery procedure to clear the bus
Wan ZongShun (1):
i2c/nuc900: add i2c driver support for nuc900
arch/arm/mach-w90x900/include/mach/i2c.h | 9 +
drivers/i2c/busses/Kconfig | 11 +-
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-davinci.c | 314 +++++++++++---
drivers/i2c/busses/i2c-nuc900.c | 709 ++++++++++++++++++++++++++++++
drivers/i2c/busses/i2c-pxa.c | 2 +-
6 files changed, 980 insertions(+), 66 deletions(-)
create mode 100644 arch/arm/mach-w90x900/include/mach/i2c.h
create mode 100644 drivers/i2c/busses/i2c-nuc900.c
reply other threads:[~2010-08-18 4:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100814150918.GA29606@ben-laptop.fluff.org \
--to=ben@trinity.fluff.org \
--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
all inboxes | Powered by JetHome®