linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark D. Studebaker" <mds@paradyne.com>
To: Joakim Tjernlund <Joakim.Tjernlund@lumentis.se>
Cc: Tom Rini <trini@kernel.crashing.org>,
	linuxppc-embedded@lists.linuxppc.org,
	sensors@stimpy.netroedge.com
Subject: Re: 8xx i2c refers to unspecified chip errata
Date: Mon, 18 Nov 2002 14:04:21 -0500	[thread overview]
Message-ID: <3DD939B5.3D1F2B6E@paradyne.com> (raw)
In-Reply-To: 20021118141042.GA15279@opus.bloom.county

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

whatever your patch was against didn't match our tree very well. would
you please
resolve the differences and generate a new patch against our tree?
thanks
mds

Tom Rini wrote:
>
> 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/

[-- Attachment #2: fail --]
[-- Type: text/plain, Size: 537 bytes --]

patching file i2c-algo-8xx.c
Hunk #1 FAILED at 7.
Hunk #2 FAILED at 27.
Hunk #3 succeeded at 74 with fuzz 2 (offset 14 lines).
Hunk #5 succeeded at 157 (offset 18 lines).
Hunk #6 FAILED at 177.
Hunk #8 succeeded at 220 (offset 18 lines).
Hunk #9 FAILED at 237.
Hunk #10 succeeded at 333 (offset 2 lines).
Hunk #11 FAILED at 343.
Hunk #12 FAILED at 359.
Hunk #13 succeeded at 439 (offset 18 lines).
Hunk #14 FAILED at 464.
Hunk #15 succeeded at 514 (offset 2 lines).
7 out of 15 hunks FAILED -- saving rejects to file i2c-algo-8xx.c.rej


  reply	other threads:[~2002-11-18 19:04 UTC|newest]

Thread overview: 30+ 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
2002-10-24 16:10               ` Tom Rini
2002-10-24 18:21                 ` Joakim Tjernlund
2002-11-01 11:01                   ` Joakim Tjernlund
2002-11-01 19:19                     ` Tom Rini
2002-11-17 20:51                   ` Mark D. Studebaker
2002-11-17 21:44                     ` Joakim Tjernlund
2002-11-18 14:10                       ` Tom Rini
2002-11-18 19:04                         ` Mark D. Studebaker [this message]
2002-11-18 19:24                           ` Joakim Tjernlund
2002-11-18 19:31                             ` Tom Rini
2002-11-18 19:42                             ` Jean Delvare
2002-11-18 19:46                               ` Tom Rini
  -- 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=3DD939B5.3D1F2B6E@paradyne.com \
    --to=mds@paradyne.com \
    --cc=Joakim.Tjernlund@lumentis.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=sensors@stimpy.netroedge.com \
    --cc=trini@kernel.crashing.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).