From: Christian Kujau <evil@g-house.de>
To: Tom Rini <trini@kernel.crashing.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.6 PReP fix? (Was: [jgarzik@pobox.com: [PATCH/CFT] de2104x fixes])
Date: Thu, 27 Nov 2003 01:01:07 +0100 [thread overview]
Message-ID: <3FC53EC3.4060302@g-house.de> (raw)
In-Reply-To: <3FC537B5.80504@g-house.de>
Christian Kujau wrote:
>
> Tom Rini wrote:
>
>> Ok, here's a better patch. It's against 2.6.0-test9-BK-latest
>> (currently bk25).
>
>
> [...]
>
> i don't have a -bk tree here, so i get a .rej with -test9 and -test10:
>
> evil@sheep:/usr/src/linux-2.6$ cat /data/Incoming/de2104x.c.diff | \
> patch -p1 --dry-run
> patching file drivers/net/tulip/de2104x.c
> Hunk #6 FAILED at 1569.
> 1 out of 7 hunks FAILED -- saving rejects to file
> drivers/net/tulip/de2104x.c.rej
> evil@sheep:/usr/src/linux-2.6$
>
but it seems to compile:
CC drivers/net/net_init.o
CC drivers/net/loopback.o
CC [M] drivers/net/tulip/de2104x.o
CC [M] drivers/net/tulip/eeprom.o
CC [M] drivers/net/tulip/interrupt.o
CC [M] drivers/net/tulip/media.o
CC [M] drivers/net/tulip/timer.o
CC [M] drivers/net/tulip/tulip_core.o
CC [M] drivers/net/tulip/21142.o
CC [M] drivers/net/tulip/pnic.o
CC [M] drivers/net/tulip/pnic2.o
LD [M] drivers/net/tulip/tulip.o
CC [M] drivers/net/tulip/de4x5.o
LD drivers/net/built-in.o
CC [M] drivers/net/3c59x.o
(compile will finish soon, but have to to sleep now, ...blip..)
Christian.
--
BOFH excuse #20:
divide-by-zero error
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-11-27 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 20:31 2.6 PReP fix? (Was: [jgarzik@pobox.com: [PATCH/CFT] de2104x fixes]) Tom Rini
2003-11-26 23:31 ` Christian Kujau
2003-11-26 23:48 ` Tom Rini
2003-11-27 0:01 ` Christian Kujau [this message]
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=3FC53EC3.4060302@g-house.de \
--to=evil@g-house.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--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 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.