linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Mattia Dongili <malattia@linux.it>
Cc: UML-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] 2.6.18 SKAS patch fails to apply (1 failed HUNK)
Date: Sun, 24 Sep 2006 21:19:17 +0200	[thread overview]
Message-ID: <200609242119.17741.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20060924114638.GB27881@inferi.kami.home>

On Sunday 24 September 2006 13:46, Mattia Dongili wrote:
> Hello Paolo,
>
> with the following change the patch applies and hopefully works, still
> building here but mm/fremap.o is done so I'm quite optimistic :) (__prot
> is used in the code, not prot).
Ok, ok, I'm doing a production release... (I used some freedom in that one, 
since it was a developer release). Or better, two production releases.
One normal one, and another with full RFP support.

As explained in the news page, the patch _requires_ the separate 
Remap_File_Pages patch (it was an experimental release); I should have 
suggested that you can simply split away the last patch in series to remove 
the dependency. Plus some requested fixups on configuration items (deprecate 
TT mode for instance).

Additionally, I'm releasing -bb1: quite a lot of improvements for locking, 
especially on UBD, but also on UML networking drivers, and on helpers 
execution, and experimental TLS x86_64 support.

> NOTE: I hope sourceforge smtp won't reject my message...

> --- ./skas-2.6.18-rc4-v9-pre9-fremap.patch.orig	2006-09-24
> 12:37:57.000000000 +0200 +++
> ./skas-2.6.18-rc4-v9-pre9-fremap.patch	2006-09-24 13:03:18.000000000 +0200
> @@ -1454,7 +1454,7 @@
>    */
>  -asmlinkage long sys_remap_file_pages(unsigned long start, unsigned long
> size, +long __remap_file_pages(struct mm_struct *mm, unsigned long start,
> unsigned long size, - 	unsigned long prot, unsigned long pgoff, unsigned
> long flags)
> + 	unsigned long __prot, unsigned long pgoff, unsigned long flags)
>   {
>  -	struct mm_struct *mm = current->mm;
>   	struct address_space *mapping;

-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade

		
___________________________________ 
Yahoo! Messenger with Voice: chiama da PC a telefono a tariffe esclusive 
http://it.messenger.yahoo.com


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2006-09-24 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-24 11:46 [uml-devel] 2.6.18 SKAS patch fails to apply (1 failed HUNK) Mattia Dongili
2006-09-24 19:19 ` Blaisorblade [this message]
2006-09-25 18:07   ` Mattia Dongili

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=200609242119.17741.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=malattia@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox