From: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: Kevin Hilman <khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
Cc: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap <linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [GIT PULL] I2C: OMAP: misc. cleanup for v3.2
Date: Tue, 4 Oct 2011 22:08:32 +0100 [thread overview]
Message-ID: <20111004210832.GC13323@freya.fluff.org> (raw)
In-Reply-To: <4E80FD1A.5040006-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
On Mon, Sep 26, 2011 at 03:30:50PM -0700, Kevin Hilman wrote:
> ping
>
> On 09/06/2011 03:31 PM, Kevin Hilman wrote:
> >Hi Ben,
> >
> >On 08/23/2011 05:10 PM, Kevin Hilman wrote:
> >>Ben,
> >>
> >>Here's one more I2C cleanup series for v3.2.
> >>
> >>It applies on top of my for_3.2/i2c-fixes branch just submitted.
> >>
> >>Please pull into your tree for linux-next.
> >
> >I see you pulled the other two, can you pull this one as well?
I've tried, but it seems to note that everything is up to date.
Is this a suitable branch to pull onto latest so I can reset
my next tree?
--
Ben
next prev parent reply other threads:[~2011-10-04 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 0:10 [GIT PULL] I2C: OMAP: misc. cleanup for v3.2 Kevin Hilman
[not found] ` <871uwbhdoj.fsf-l0cyMroinI0@public.gmane.org>
2011-09-06 22:31 ` Kevin Hilman
[not found] ` <4E669F36.2070008-l0cyMroinI0@public.gmane.org>
2011-09-12 17:39 ` Kevin Hilman
2011-09-26 22:30 ` Kevin Hilman
[not found] ` <4E80FD1A.5040006-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2011-10-04 21:08 ` Ben Dooks [this message]
[not found] ` <20111004210832.GC13323-RazCHl0VsYgkUSuvROHNpA@public.gmane.org>
2011-10-05 16:11 ` Kevin Hilman
2011-10-09 11:35 ` Ming Lei
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=20111004210832.GC13323@freya.fluff.org \
--to=ben-i2c-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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).