From: "roland" <for_spam@gmx.de>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Patch for 2.6.6
Date: Wed, 12 May 2004 23:20:35 +0200 [thread overview]
Message-ID: <101901c43866$f7e64720$2000000a@schlepptopp> (raw)
In-Reply-To: 200405122024.22702.blaisorblade_spam@yahoo.it
hey,
2.6.6-um1 up and running here!
thanks paolo!
this is what i did:
-download 2.6.6 vanilla kernel
-patch with http://www.user-mode-linux.org/~blaisorblade/patches/uml-patch-2.6.6-02.bz2
-patch with http://www.user-mode-linux.org/~blaisorblade/patches/patch-2.6.6-v2
a while ago i mentioned:
"make allmodconfig ARCH=um" is broken
see: http://marc.theaimsgroup.com/?l=user-mode-linux-user&m=108250926319847&w=2
any hints for fixing this ?
regards
roland
----- Original Message -----
From: "BlaisorBlade" <blaisorblade_spam@yahoo.it>
To: <user-mode-linux-devel@lists.sourceforge.net>
Sent: Wednesday, May 12, 2004 8:24 PM
Subject: Re: [uml-devel] Patch for 2.6.6
Alle 22:28, martedì 11 maggio 2004, Dennis Muhlestein ha scritto:
> I got this:
>
> Reversed (or previously applied) patch detected! Assume -R? [n]
> Apply anyway? [n] y
> Hunk #1 FAILED at 1.
> Hunk #2 FAILED at 19.
> 2 out of 2 hunks FAILED -- saving rejects to file include/asm-um/irq.h.rej
>
> when applying the first patch. I tried also with not applying that
> part, and get a compile failure pretty early in the build process.
>
> -Dennis
Ok, I botched that part, sorry - try with the patch from Jeff Chua. I'm
posting on the site the corrected version, which I hope should apply
perfectly (I've tested it on apply and unapply - the first one come by making
it work on reversing without rejects the Jeff Chua's version).
And, finally, also I should quit editing patches by hand :-), maybe!
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=dnemail3
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-05-12 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 18:37 [uml-devel] Patch for 2.6.6 BlaisorBlade
2004-05-11 20:28 ` Dennis Muhlestein
2004-05-11 23:22 ` roland
2004-05-12 18:24 ` BlaisorBlade
2004-05-12 21:20 ` roland [this message]
2004-05-12 13:39 ` Rik van Riel
2004-05-15 15:03 ` /dev/rob0
-- strict thread matches above, loose matches on Subject: below --
2004-05-11 19:01 BlaisorBlade
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='101901c43866$f7e64720$2000000a@schlepptopp' \
--to=for_spam@gmx.de \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.