From: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Subject: Please pull bjdooks' i2c-fixes
Date: Thu, 20 Aug 2009 22:32:29 +0100 [thread overview]
Message-ID: <E1MeFFF-0003wj-Iw@kira.home.fluff.org> (raw)
The following changes since commit 64f1607ffbbc772685733ea63e6f7f4183df1b16:
Linus Torvalds (1):
Linux 2.6.31-rc6
are available in the git repository at:
git://aeryn.fluff.org.uk/bjdooks/linux.git i2c-fixes-rc6
Linus Walleij (1):
i2c-stu300: I2C STU300 stability updates
Moiz Sonasath (2):
i2c-omap: ACK pending [R/X]DR and [R/X]RDY interrupts
i2c-omap: Enable workaround for Errata 1.153 based on
Nishanth Menon (1):
i2c-omap: Fix I2C status ACK
drivers/i2c/busses/i2c-omap.c | 14 +++-
drivers/i2c/busses/i2c-stu300.c | 157 +++++++++++++++++++++++----------------
2 files changed, 104 insertions(+), 67 deletions(-)
next reply other threads:[~2009-08-20 21:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 21:32 Ben Dooks [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-18 0:31 Please pull bjdooks' i2c-fixes Ben Dooks
2010-09-30 23:04 Ben Dooks
2010-10-01 8:09 ` Wolfram Sang
[not found] ` <20101001080951.GA27870-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-10-06 22:14 ` Ben Dooks
[not found] ` <20101006221430.GW21564-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-10-07 6:43 ` Wolfram Sang
2010-09-22 1:11 Ben Dooks
2010-01-24 15:33 Ben Dooks
2009-12-24 1:59 Ben Dooks
2009-07-30 0:06 Ben Dooks
2009-07-14 23:06 Ben Dooks
2009-05-11 23:42 Ben Dooks
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=E1MeFFF-0003wj-Iw@kira.home.fluff.org \
--to=ben-linux-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-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).