From: Mike Frysinger <vapier.adi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ben Dooks <ben-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Subject: Re: [Uclinux-dist-devel] [PATCH 3/4] i2c-bfin-twi: remove redundant retry
Date: Wed, 23 Dec 2009 20:39:01 -0500 [thread overview]
Message-ID: <8bd0f97a0912231739k7e8de6ecpa5a0c215b9942e33@mail.gmail.com> (raw)
In-Reply-To: <20091224012537.GA10442-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
On Wed, Dec 23, 2009 at 20:25, Ben Dooks wrote:
> On Mon, Dec 21, 2009 at 09:28:32AM -0500, Mike Frysinger wrote:
>> From: Sonic Zhang <sonic.zhang-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>
>
> Failed to apply, not had a look at why.
the presumption is that you applied the previous two patches i sent
out some time ago
or just pull all our pending changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/vapier/blackfin.git for-i2c
-mike
next prev parent reply other threads:[~2009-12-24 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 14:28 [PATCH 1/4] i2c-bfin-twi: fix CLKDIV calculation Mike Frysinger
[not found] ` <1261405713-7262-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-12-21 14:28 ` [PATCH 2/4] i2c-bfin-twi: fix lost interrupts at high speeds Mike Frysinger
2009-12-21 14:28 ` [PATCH 3/4] i2c-bfin-twi: remove redundant retry Mike Frysinger
[not found] ` <1261405713-7262-3-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-12-24 1:25 ` Ben Dooks
[not found] ` <20091224012537.GA10442-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-12-24 1:39 ` Mike Frysinger [this message]
2009-12-21 14:28 ` [PATCH 4/4] i2c-bfin-twi: return completion in interrupt for smbus quick transfers Mike Frysinger
2009-12-21 14:29 ` [Uclinux-dist-devel] [PATCH 1/4] i2c-bfin-twi: fix CLKDIV calculation Mike Frysinger
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=8bd0f97a0912231739k7e8de6ecpa5a0c215b9942e33@mail.gmail.com \
--to=vapier.adi-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ben-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+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).