mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] remove *_segments() dummy functions again
Date: Thu, 26 Jun 2003 11:32:17 +0100	[thread overview]
Message-ID: <20030626103217.GJ451@parcelfarce.linux.theplanet.co.uk> (raw)


Hi Linus.  Back on 4th November you applied a patch to remove the
now-unused *_segments() functions from all architectures ... but some
of the newer architecures still have them.  Please apply.

 asm-arm26/processor.h  |    4 ----
 asm-h8300/processor.h  |    3 ---
 asm-x86_64/processor.h |    2 --
 3 files changed, 9 deletions(-)

Index: include/asm-arm26/processor.h
===================================================================
RCS file: /var/cvs/linux-2.5/include/asm-arm26/processor.h,v
retrieving revision 1.2
diff -u -p -r1.2 processor.h
--- include/asm-arm26/processor.h	14 Jun 2003 22:15:54 -0000	1.2
+++ include/asm-arm26/processor.h	26 Jun 2003 10:24:47 -0000
@@ -100,10 +100,6 @@ struct task_struct;
 /* Free all resources held by a thread. */
 extern void release_thread(struct task_struct *);
 
-/* Copy and release all segment info associated with a VM */
-#define copy_segments(tsk, mm)		do { } while (0)
-#define release_segments(mm)		do { } while (0)
-
 unsigned long get_wchan(struct task_struct *p);
 
 #define cpu_relax()			barrier()
Index: include/asm-h8300/processor.h
===================================================================
RCS file: /var/cvs/linux-2.5/include/asm-h8300/processor.h,v
retrieving revision 1.2
diff -u -p -r1.2 processor.h
--- include/asm-h8300/processor.h	24 Apr 2003 01:37:23 -0000	1.2
+++ include/asm-h8300/processor.h	26 Jun 2003 10:24:47 -0000
@@ -89,9 +89,6 @@ static inline void release_thread(struct
 
 extern int kernel_thread(int (*fn)(void *), void * arg, unsigned long flags);
 
-#define copy_segments(tsk, mm)	do { } while (0)
-#define release_segments(mm)	do { } while (0)
-#define forget_segments()	do { } while (0)
 #define prepare_to_copy(tsk)	do { } while (0)
 
 /*
Index: include/asm-x86_64/processor.h
===================================================================
RCS file: /var/cvs/linux-2.5/include/asm-x86_64/processor.h,v
retrieving revision 1.14
diff -u -p -r1.14 processor.h
--- include/asm-x86_64/processor.h	14 Jun 2003 22:16:00 -0000	1.14
+++ include/asm-x86_64/processor.h	26 Jun 2003 10:24:47 -0000
@@ -280,8 +280,6 @@ extern void prepare_to_copy(struct task_
  */
 extern long kernel_thread(int (*fn)(void *), void * arg, unsigned long flags);
 
-static inline void release_segments(struct mm_struct *mm) { }
-
 /*
  * Return saved PC of a blocked thread.
  * What is this good for? it will be always the scheduler or ret_from_fork.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

                 reply	other threads:[~2003-06-26 10:18 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=20030626103217.GJ451@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®