From: Jean Delvare <khali@linux-fr.org>
To: Domen Puncer <domen.puncer@telargo.com>
Cc: i2c@lm-sensors.org, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] i2c-mpc: work around missing-9th-clock-pulse bug
Date: Wed, 11 Jul 2007 13:40:37 +0200 [thread overview]
Message-ID: <20070711134037.1fe0373e@hyperion.delvare> (raw)
In-Reply-To: <20070711063335.GB4375@moe.telargo.com>
Hi Domen,
On Wed, 11 Jul 2007 08:33:35 +0200, Domen Puncer wrote:
> On 11/07/07 00:03 -0600, Grant Likely wrote:
> > I don't think it's a great idea to use a link; You should copy the
> > important parts into the .c file. Archives may not be forever, and
> > links cannot be read when offline. If the text is too long for the
> > middle of the C file; then put the documentation at the top right
> > after the header block.
>
> And v4:
> <----------- cut ------------->
>
> Work around a problem reported on:
> http://ozlabs.org/pipermail/linuxppc-embedded/2005-July/019038.html
> Without this patch I2C on mpc5200 becomes unusable after a while.
> Tested on mpc5200 boards by Matthias Fechner and me.
>
>
> Signed-off-by: Domen Puncer <domen.puncer@telargo.com>
Applied, thanks.
--
Jean Delvare
next prev parent reply other threads:[~2007-07-11 11:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 7:19 [PATCH] i2c-mpc: work around missing-9th-clock-pulse bug Domen Puncer
2007-07-09 15:53 ` Grant Likely
2007-07-10 6:17 ` Domen Puncer
2007-07-10 6:22 ` Grant Likely
2007-07-10 12:40 ` Jean Delvare
2007-07-11 5:49 ` Domen Puncer
2007-07-11 6:03 ` Grant Likely
2007-07-11 6:33 ` Domen Puncer
2007-07-11 11:40 ` Jean Delvare [this message]
2007-07-21 0:03 ` [i2c] " Guennadi Liakhovetski
2007-07-24 5:14 ` [PATCH] i2c-mpc: don't disable I2C module on stop condition Domen Puncer
2007-08-08 17:19 ` Jean Delvare
2007-08-08 18:33 ` Guennadi Liakhovetski
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=20070711134037.1fe0373e@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=domen.puncer@telargo.com \
--cc=i2c@lm-sensors.org \
--cc=linuxppc-embedded@ozlabs.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.