From: trini@kernel.crashing.org (Tom Rini)
To: Joakim Tjernlund <Joakim.Tjernlund@lumentis.se>
Cc: "Mark D. Studebaker" <mds@paradyne.com>,
linuxppc-embedded@lists.linuxppc.org,
sensors@stimpy.netroedge.com
Subject: 8xx i2c refers to unspecified chip errata
Date: Thu, 19 May 2005 06:23:41 +0000 [thread overview]
Message-ID: <20021118141042.GA15279@opus.bloom.county> (raw)
In-Reply-To: <001101c28e82$88d2bc40$0200a8c0@telia.com>
On Sun, Nov 17, 2002 at 10:44:40PM +0100, Joakim Tjernlund wrote:
> > Tom + Joakim,
> > we're doing a release soon over here at sensors/i2c,
> > do you want this checked in as-is, with mods, or not at all?
>
> As-is for me. No problems reported to me.
Works for me then.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
WARNING: multiple messages have this Message-ID (diff)
From: Tom Rini <trini@kernel.crashing.org>
To: Joakim Tjernlund <Joakim.Tjernlund@lumentis.se>
Cc: "Mark D. Studebaker" <mds@paradyne.com>,
linuxppc-embedded@lists.linuxppc.org,
sensors@stimpy.netroedge.com
Subject: Re: 8xx i2c refers to unspecified chip errata
Date: Mon, 18 Nov 2002 07:10:42 -0700 [thread overview]
Message-ID: <20021118141042.GA15279@opus.bloom.county> (raw)
In-Reply-To: <001101c28e82$88d2bc40$0200a8c0@telia.com>
On Sun, Nov 17, 2002 at 10:44:40PM +0100, Joakim Tjernlund wrote:
> > Tom + Joakim,
> > we're doing a release soon over here at sensors/i2c,
> > do you want this checked in as-is, with mods, or not at all?
>
> As-is for me. No problems reported to me.
Works for me then.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2005-05-19 6:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 20:14 8xx i2c refers to unspecified chip errata Barker Michael-r43496
2002-10-10 10:35 ` Joakim Tjernlund
2002-10-10 16:18 ` Dan Malek
2002-10-10 16:35 ` Dr. Craig Hollabaugh
2002-10-11 7:28 ` Joakim Tjernlund
2002-10-11 7:50 ` bart
2002-10-11 9:12 ` Joakim Tjernlund
2002-10-11 9:56 ` bart
2002-10-11 12:02 ` Stephan Linke
2002-10-11 12:14 ` bart
2002-10-11 12:31 ` Stephan Linke
2002-10-11 12:46 ` Joakim Tjernlund
2002-10-11 12:44 ` Joakim Tjernlund
2002-10-11 12:55 ` bart
2002-10-11 13:10 ` Joakim Tjernlund
2002-10-15 16:57 ` Tom Rini
2002-10-22 9:15 ` Joakim Tjernlund
2005-05-19 6:23 ` Joakim Tjernlund
2002-10-24 16:10 ` Tom Rini
2005-05-19 6:23 ` Tom Rini
2002-10-24 18:21 ` Joakim Tjernlund
2005-05-19 6:23 ` Joakim Tjernlund
2002-11-01 11:01 ` Joakim Tjernlund
2002-11-01 19:19 ` Tom Rini
2002-11-17 20:51 ` Mark D. Studebaker
2005-05-19 6:23 ` Mark D. Studebaker
2002-11-17 21:44 ` Joakim Tjernlund
2002-11-18 14:10 ` Tom Rini [this message]
2005-05-19 6:23 ` Tom Rini
2002-11-18 19:04 ` Mark D. Studebaker
2005-05-19 6:23 ` Mark D. Studebaker
2002-11-18 19:24 ` Joakim Tjernlund
2005-05-19 6:23 ` Joakim Tjernlund
2002-11-18 19:31 ` Tom Rini
2005-05-19 6:23 ` Tom Rini
2002-11-18 19:42 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2002-11-18 19:46 ` Tom Rini
2005-05-19 6:23 ` Tom Rini
2005-05-19 6:23 ` Joakim Tjernlund
2005-05-19 6:23 ` Tom Rini
2005-05-19 6:23 ` Mark D. Studebaker
-- strict thread matches above, loose matches on Subject: below --
2002-10-10 17:01 Barker Michael-r43496
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=20021118141042.GA15279@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=Joakim.Tjernlund@lumentis.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mds@paradyne.com \
--cc=sensors@stimpy.netroedge.com \
/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.