Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, Martin Michlmayr <tbm@cyrius.com>
Subject: Re: SGI O2 meth: missing sysfs device symlink
Date: Tue, 22 May 2007 14:13:11 +0200	[thread overview]
Message-ID: <1179835991.7896.32.camel@scarafaggio> (raw)
In-Reply-To: <1179834093.7896.23.camel@scarafaggio>

Il giorno mar, 22/05/2007 alle 13.41 +0200, Giuseppe Sacco ha scritto:
> Il giorno mar, 22/05/2007 alle 12.09 +0100, Ralf Baechle ha scritto:
> > On Mon, May 21, 2007 at 04:47:26PM +0100, Ralf Baechle wrote:
> > 
> > Below patch is meant to cure the problem.  It's against HEAD but should
> > apply to somewhat older problems as well.
> > 
> > I appreciate testing asap so I can try to still push this upstream
> > for 2.6.22.
> [...]
> 
> I may test it against 2.6.18, the standard debian kernel for stable; but
> I will be on the console only in two days :-(

It seems the patch doesn't apply on 2.6.18, so I will recompile
2.6.22-rc2, but I do not know if it works on my SGI. I never tried it.

The error is:

giuseppe@sgi:/usr/local/src/linux-source-2.6.18$ patch -p1 --dry-run </tmp/sgi.patch 
patching file arch/mips/sgi-ip32/Makefile
Hunk #1 succeeded at 3 with fuzz 2.
patching file arch/mips/sgi-ip32/ip32-platform.c
patching file drivers/net/meth.c
Hunk #1 FAILED at 8.
Hunk #2 succeeded at 36 with fuzz 2 (offset 2 lines).
Hunk #3 succeeded at 53 (offset 2 lines).
Hunk #4 succeeded at 785 (offset 3 lines).
Hunk #5 succeeded at 809 with fuzz 2 (offset 3 lines).
Hunk #6 succeeded at 822 (offset 3 lines).
1 out of 6 hunks FAILED -- saving rejects to file drivers/net/meth.c.rej

  parent reply	other threads:[~2007-05-22 12:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1178743456.15447.41.camel@scarafaggio>
     [not found] ` <20070516151939.GH19816@deprecation.cyrius.com>
     [not found]   ` <20070516160313.GA3409@bongo.bofh.it>
     [not found]     ` <50621.192.168.2.50.1179383217.squirrel@eppesuigoccas.homedns.org>
2007-05-17 15:16       ` SGI O2 meth: missing sysfs device symlink Martin Michlmayr
2007-05-21 15:47         ` Ralf Baechle
2007-05-22 11:09           ` Ralf Baechle
2007-05-22 11:41             ` Giuseppe Sacco
2007-05-22 12:01               ` sknauert
2007-05-22 12:28                 ` Ralf Baechle
2007-05-22 13:32                   ` sknauert
2007-05-22 15:18                     ` Thiemo Seufer
2007-05-22 16:46                       ` Cross-Compile difficulties sknauert
2007-05-22 17:32                         ` Geert Uytterhoeven
2007-05-22 22:44                           ` sknauert
2007-05-22 23:26                             ` Carlos Munoz
2007-05-23  3:42                             ` Kumba
2007-05-23 17:41                               ` sknauert
2007-05-23  6:12                             ` Geert Uytterhoeven
2007-05-22 13:02                 ` SGI O2 meth: missing sysfs device symlink Thiemo Seufer
2007-05-22 12:13               ` Giuseppe Sacco [this message]
2007-05-22 13:00                 ` Ralf Baechle
2007-05-23 11:45                 ` Giuseppe Sacco
2007-05-24 11:47                   ` Ralf Baechle
2007-05-23  3:51             ` Kumba
2007-05-23  8:37               ` Ralf Baechle

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=1179835991.7896.32.camel@scarafaggio \
    --to=giuseppe@eppesuigoccas.homedns.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tbm@cyrius.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox