Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Cc: linux-mips@linux-mips.org, Martin Michlmayr <tbm@cyrius.com>
Subject: Re: SGI O2 meth: missing sysfs device symlink
Date: Thu, 24 May 2007 12:47:23 +0100	[thread overview]
Message-ID: <20070524114723.GA27073@linux-mips.org> (raw)
In-Reply-To: <1179920735.6770.6.camel@scarafaggio>

On Wed, May 23, 2007 at 01:45:35PM +0200, Giuseppe Sacco wrote:

> I got 2.6.21.1 source, then I applied patch-2.6.22-rc2.bz2 and your
> patch. I compiled everything with this command:
> 
> # make-kpkg clean
> # time make-kpkg --revision 2:2.6.22~rc2 \
> -append-to-version -r5k-ip32 --arch-in-name buildpackage
> 
> and got this result:
> 
> [...]
>   CC [M]  net/ipv6/reassembly.o
>   CC [M]  net/ipv6/tcp_ipv6.o
>   CC [M]  net/ipv6/exthdrs.o
> net/ipv6/exthdrs.c: In function ‘ipv6_rthdr_rcv’:
> net/ipv6/exthdrs.c:390: error: ‘struct sk_buff’ has no member named ‘h’
> net/ipv6/exthdrs.c:391: error: ‘struct sk_buff’ has no member named ‘h’
> net/ipv6/exthdrs.c:391: error: ‘struct sk_buff’ has no member named ‘h’
> net/ipv6/exthdrs.c:398: error: ‘struct sk_buff’ has no member named ‘h’
> make[4]: *** [net/ipv6/exthdrs.o] Error 1
> make[3]: *** [net/ipv6] Error 2
> make[2]: *** [net] Error 2
> make[2]: Leaving directory `/home/src/linux-2.6.22-rc2'
> make[1]: *** [debian/stamp-build-kernel] Error 2
> make[1]: Leaving directory `/home/src/linux-2.6.22-rc2'
> make: *** [stamp-buildpackage] Error 2
> 
> real    409m49.142s
> user    250m33.296s
> sys     15m41.356s
> sgi:/usr/local/src/linux-2.6.22-rc2# bc

Unrelated problem.  If you can reproduce it with a vanilla kernel report
to netdev@vger.kernel.org.

  Ralf

  Ralf

  reply	other threads:[~2007-05-24 11:47 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
2007-05-22 13:00                 ` Ralf Baechle
2007-05-23 11:45                 ` Giuseppe Sacco
2007-05-24 11:47                   ` Ralf Baechle [this message]
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=20070524114723.GA27073@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=giuseppe@eppesuigoccas.homedns.org \
    --cc=linux-mips@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