From: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: i2c fixes for 2.6.30-rc5
Date: Sun, 3 May 2009 23:36:56 +0100 [thread overview]
Message-ID: <20090503223656.GA12866@fluff.org.uk> (raw)
Currently, I've got the following in my tree, if anyone
thinks i've missed anything, then let me know before the end
of Tuesday (5th) and I'll add it to the pull request.
The following changes since commit 091438dd5668396328a3419abcbc6591159eb8d1:
Linus Torvalds (1):
Linux 2.6.30-rc4
are available in the git repository at:
git://aeryn.fluff.org.uk/bjdooks/linux.git i2c-for-2630-rc5
Mark Brown (1):
i2c: Enable i2c-s3c2410 for S3C64XX too
Mark Ware (1):
i2c-cpm: Pass dev ptr to dma_*_coherent rather than NULL
Roel Kluin (1):
i2c-pxa.c: timeouts off by 1
Wolfgang Grandegger (1):
i2c: i2c-mpc: bug fix for MPC52xx clock setting and printout
drivers/i2c/busses/Kconfig | 2 +-
drivers/i2c/busses/i2c-cpm.c | 16 ++++++++--------
drivers/i2c/busses/i2c-mpc.c | 34 ++++++++++++++++++++--------------
drivers/i2c/busses/i2c-pxa.c | 6 +++---
4 files changed, 32 insertions(+), 26 deletions(-)
reply other threads:[~2009-05-03 22:36 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=20090503223656.GA12866@fluff.org.uk \
--to=ben-linux-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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