From: AnonimoVeneziano <voloterreno@tin.it>
To: black666@inode.at
Cc: linux-kernel@vger.kernel.org
Subject: Re: vt8235 fix, hopefully last variant
Date: Tue, 24 Dec 2002 01:33:17 +0100 [thread overview]
Message-ID: <3E07AB4D.8030703@tin.it> (raw)
In-Reply-To: <200212240126.46794.black666@inode.at>
Patrick Petermair wrote:
>AnonimoVeneziano:
>
>
>
>>>What is it exactly that doesn't work? The patching, compiling,
>>>booting, dma,...?
>>>
>>>
>>>
>>The patching .... it said something about HUNKS failed....
>>
>>
>
>It's normal that Hunk 1 and 2 fail... Hunk 3 is the important one. So
>you can compile the kernel even with Hunks 1&2 failing.
>
>Quote from Vojtech:
>-----
>
>
>
>>I tried the last patch, but it didn't work - I got Hunk messages:
>>
>>starbase:/usr/src/linux-2.4.20# patch -p1 < vt8235-atapi
>>patching file drivers/ide/via82cxxx.c
>>Hunk #1 FAILED at 1.
>>Hunk #2 FAILED at 141.
>>Hunk #3 succeeded at 283 (offset -57 lines).
>>2 out of 3 hunks FAILED -- saving rejects to file
>>starbase:/usr/src/linux-2.4.20#
>>
>>
>
>Since they're in comments only, you can ignore them.
>
>-----
>
>Patrick
>
>
>
>
Ah, ok, thank you very much, tomorrow I'll try to compile.I've tried to
compile the patch vt8235-min (with 2 hunks failed) but It wasn't work.
With vt8235-atapi I haven't tried at all when I've saw the failed hunks.
I haven't compile.
Thank you
Bye
Marcello
next prev parent reply other threads:[~2002-12-24 0:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 10:26 vt8235 fix, hopefully last variant Vojtech Pavlik
2002-12-19 13:34 ` AnonimoVeneziano
2002-12-19 17:41 ` John Reiser
2002-12-20 20:12 ` Patrick Petermair
2002-12-21 9:21 ` Vojtech Pavlik
2002-12-21 10:51 ` Patrick Petermair
2002-12-21 12:00 ` Vojtech Pavlik
2002-12-21 0:25 ` Christian Seidemann
2002-12-23 19:30 ` AnonimoVeneziano
2002-12-23 21:42 ` Patrick Petermair
2002-12-24 0:09 ` AnonimoVeneziano
2002-12-24 0:26 ` Patrick Petermair
2002-12-24 0:33 ` AnonimoVeneziano [this message]
2002-12-21 17:57 ` John Reiser
2002-12-21 18:27 ` Vojtech Pavlik
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=3E07AB4D.8030703@tin.it \
--to=voloterreno@tin.it \
--cc=black666@inode.at \
--cc=linux-kernel@vger.kernel.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.