From: Ben Dooks <ben-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: what is in bjdooks' i2c-fixes tree
Date: Tue, 02 Jun 2009 23:45:11 +0100 [thread overview]
Message-ID: <E1MBcjH-0003Zr-TI@kira.home.fluff.org> (raw)
The following changes since commit 05ad709d04799125ed85dd816fdb558258102172:
Alan Cox (1):
parport: quickfix the proc registration bug
are available in the git repository at:
git://aeryn.fluff.org.uk/bjdooks/linux.git i2c-fixes-2630-rc7
Aaro Koskinen (2):
i2c: OMAP2/3: Fix scll/sclh calculations
i2c: OMAP3: Better noise suppression for fast/standard modes
Frank Shew (1):
i2c: Blackfin TWI: fix transfer errors with repeat start
Michael Hennerich (2):
i2c: Blackfin TWI: make sure we don't end up with a CLKDIV=0
i2c: Blackfin TWI: implement I2C_FUNC_SMBUS_I2C_BLOCK functionality
Sonic Zhang (1):
i2c: Blackfin TWI: fix REPEAT START mode doesn't repeat
drivers/i2c/busses/Kconfig | 2 +-
drivers/i2c/busses/i2c-bfin-twi.c | 59 +++++++++++++++++++++++++-----------
drivers/i2c/busses/i2c-omap.c | 39 +++++++++++++++++++-----
3 files changed, 72 insertions(+), 28 deletions(-)
reply other threads:[~2009-06-02 22:45 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=E1MBcjH-0003Zr-TI@kira.home.fluff.org \
--to=ben-elnmno+kys3pigct6eibzw@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;
as well as URLs for NNTP newsgroup(s).