linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] [RFC PATCH 8/9] SKAS4 - rename new_mm
Date: Wed, 9 Jan 2008 17:09:54 -0500	[thread overview]
Message-ID: <20080109220954.GA9134@c2.user-mode-linux.org> (raw)

UML already had a new_mm().  This is renamed to make_new_mm().

Index: linux-2.6-skas4/arch/um/include/skas/skas.h
===================================================================
--- linux-2.6-skas4.orig/arch/um/include/skas/skas.h	2008-01-09 16:22:13.000000000 -0500
+++ linux-2.6-skas4/arch/um/include/skas/skas.h	2008-01-09 16:22:57.000000000 -0500
@@ -15,7 +15,7 @@ extern int skas_needs_stub;
 extern int user_thread(unsigned long stack, int flags);
 extern void new_thread_handler(void);
 extern void handle_syscall(struct uml_pt_regs *regs);
-extern int new_mm(unsigned long stack);
+extern int make_new_mm(unsigned long stack);
 extern void get_skas_faultinfo(int pid, struct faultinfo * fi);
 extern long execute_syscall_skas(void *r);
 extern unsigned long current_stub_stack(void);
Index: linux-2.6-skas4/arch/um/kernel/skas/mmu.c
===================================================================
--- linux-2.6-skas4.orig/arch/um/kernel/skas/mmu.c	2008-01-09 16:22:13.000000000 -0500
+++ linux-2.6-skas4/arch/um/kernel/skas/mmu.c	2008-01-09 16:24:05.000000000 -0500
@@ -101,7 +101,7 @@ int init_new_context(struct task_struct 
 		from_mm = &current->mm->context;
 
 	if (proc_mm) {
-		ret = new_mm(stack);
+		ret = make_new_mm(stack);
 		if (ret < 0) {
 			printk(KERN_ERR "init_new_context_skas - "
 			       "new_mm failed, errno = %d\n", ret);
Index: linux-2.6-skas4/arch/um/kernel/skas/process.c
===================================================================
--- linux-2.6-skas4.orig/arch/um/kernel/skas/process.c	2008-01-09 16:22:13.000000000 -0500
+++ linux-2.6-skas4/arch/um/kernel/skas/process.c	2008-01-09 16:24:05.000000000 -0500
@@ -9,7 +9,7 @@
 #include "os.h"
 #include "skas.h"
 
-int new_mm(unsigned long stack)
+int make_new_mm(unsigned long stack)
 {
 	int fd;
 
Index: linux-2.6-skas4/arch/um/sys-i386/ldt.c
===================================================================
--- linux-2.6-skas4.orig/arch/um/sys-i386/ldt.c	2008-01-09 16:22:13.000000000 -0500
+++ linux-2.6-skas4/arch/um/sys-i386/ldt.c	2008-01-09 16:24:05.000000000 -0500
@@ -436,7 +436,7 @@ long init_new_ldt(struct mm_context *new
 		/*
 		 * We have a valid from_mm, so we now have to copy the LDT of
 		 * from_mm to new_mm, because using proc_mm an new mm with
-		 * an empty/default LDT was created in new_mm()
+		 * an empty/default LDT was created in make_new_mm()
 		 */
 		copy = ((struct proc_mm_op) { .op 	= MM_COPY_SEGMENTS,
 					      .u 	=

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
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:[~2008-01-09 22:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080109220954.GA9134@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --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