From: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: Jochen Friedrich <jochen-NIgtFMG+Po8@public.gmane.org>
Cc: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
linuxppc-dev list
<linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
Mike Ditto <mditto-Vjf7OWgA3BLqlBn2x/YWAg@public.gmane.org>,
Kumar Gala
<galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Subject: Re: Please pull bjdoo ks' i2c-fixes
Date: Thu, 18 Dec 2008 10:06:35 +0000 [thread overview]
Message-ID: <20081218100635.GH8032@fluff.org.uk> (raw)
In-Reply-To: <4948E89A.7080703-NIgtFMG+Po8@public.gmane.org>
On Wed, Dec 17, 2008 at 12:55:06PM +0100, Jochen Friedrich wrote:
> Hi Ben,
>
> > Mike Ditto (1):
> > i2c-cpm: Detect and report NAK right away instead of timing out
>
> Could you also have a look at http://patchwork.ozlabs.org/patch/7452/ ?
> (Discussion at http://patchwork.ozlabs.org/patch/6666/ )
>
> IIRC, Kumar prefers to push this via your tree.
Ok, but this isn't really a fix, so I'll look at putting it into my
i2c-next tree, not i2c-fixes.
--
Ben (ben-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
WARNING: multiple messages have this Message-ID (diff)
From: Ben Dooks <ben-linux@fluff.org>
To: Jochen Friedrich <jochen@scram.de>
Cc: Mike Ditto <mditto@consentry.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
linux-i2c@vger.kernel.org, Ben Dooks <ben-linux@fluff.org>,
khali@linux-fr.org, torvalds@linux-foundation.org
Subject: Re: Please pull bjdoo ks' i2c-fixes
Date: Thu, 18 Dec 2008 10:06:35 +0000 [thread overview]
Message-ID: <20081218100635.GH8032@fluff.org.uk> (raw)
In-Reply-To: <4948E89A.7080703@scram.de>
On Wed, Dec 17, 2008 at 12:55:06PM +0100, Jochen Friedrich wrote:
> Hi Ben,
>
> > Mike Ditto (1):
> > i2c-cpm: Detect and report NAK right away instead of timing out
>
> Could you also have a look at http://patchwork.ozlabs.org/patch/7452/ ?
> (Discussion at http://patchwork.ozlabs.org/patch/6666/ )
>
> IIRC, Kumar prefers to push this via your tree.
Ok, but this isn't really a fix, so I'll look at putting it into my
i2c-next tree, not i2c-fixes.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2008-12-18 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 21:13 Please pull bjdoo ks' i2c-fixes Ben Dooks
[not found] ` <E1LChEf-0000Ts-53-fIsYBodh/r28n8r38hOLvmD2FQJk+8+b@public.gmane.org>
2008-12-17 11:55 ` Jochen Friedrich
2008-12-17 11:55 ` Jochen Friedrich
[not found] ` <4948E89A.7080703-NIgtFMG+Po8@public.gmane.org>
2008-12-18 10:06 ` Ben Dooks [this message]
2008-12-18 10:06 ` Ben Dooks
[not found] ` <20081218100635.GH8032-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-12-18 11:12 ` Jochen Friedrich
2008-12-18 11:12 ` Jochen Friedrich
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=20081218100635.GH8032@fluff.org.uk \
--to=ben-linux-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
--cc=galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org \
--cc=jochen-NIgtFMG+Po8@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=mditto-Vjf7OWgA3BLqlBn2x/YWAg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.