From: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: apkm-LbGehh/F0aFj/JC5u5XAOISLwOllVvif@public.gmane.org,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Subject: Please pull bjdooks' i2c tree
Date: Sat, 19 Sep 2009 23:46:44 +0100 [thread overview]
Message-ID: <E1Mp8hY-0006EA-7X@kira.home.fluff.org> (raw)
The following changes since commit 78f28b7c555359c67c2a0d23f7436e915329421e:
Linus Torvalds (1):
Merge branch 'x86-platform-for-linus' of git://git.kernel.org/.../tip/linux-2.6-tip
are available in the git repository at:
git://aeryn.fluff.org.uk/bjdooks/linux.git next-i2c
Mikael Pettersson (1):
i2c-mv64xxx: correct mv64xxx_i2c_intr() return type
Wolfram Sang (1):
i2c-imx: make bus available early
drivers/i2c/busses/i2c-imx.c | 3 +--
drivers/i2c/busses/i2c-mv64xxx.c | 4 ++--
2 files changed, 3 insertions(+), 4 deletions(-)
next reply other threads:[~2009-09-19 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 22:46 Ben Dooks [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-09 0:21 Please pull bjdooks' i2c tree Ben Dooks
2009-06-22 0:50 Ben Dooks
2009-06-16 21:45 Ben Dooks
2009-06-13 10:00 Ben Dooks
2009-03-31 22:50 Ben Dooks
[not found] ` <E1Lomn2-0002o8-Vo-fIsYBodh/r28n8r38hOLvmD2FQJk+8+b@public.gmane.org>
2009-04-01 22:57 ` Guennadi Liakhovetski
[not found] ` <Pine.LNX.4.64.0904020056550.5389-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2009-04-02 8:19 ` Wolfram Sang
2008-07-28 15:05 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=E1Mp8hY-0006EA-7X@kira.home.fluff.org \
--to=ben-linux-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
--cc=apkm-LbGehh/F0aFj/JC5u5XAOISLwOllVvif@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-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).