From: David Gibson <david@gibson.dropbear.id.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Anton Blanchard <anton@samba.org>,
linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org
Subject: [PPC64] Remove useless argument from __ste_allocate()
Date: Mon, 2 Feb 2004 17:03:32 +1100 [thread overview]
Message-ID: <20040202060332.GA17234@zax> (raw)
In the current ppc64 code the function __ste_allocate() in
arch/ppc64/mm/stab.c takes a context parameter which is never used.
This patch removes it.
Index: working-2.6/arch/ppc64/kernel/stab.c
===================================================================
--- working-2.6.orig/arch/ppc64/kernel/stab.c 2004-02-02 10:44:47.000000000 +1100
+++ working-2.6/arch/ppc64/kernel/stab.c 2004-02-02 14:10:56.755034224 +1100
@@ -142,8 +142,7 @@
return (global_entry | (castout_entry & 0x7));
}
-static inline void __ste_allocate(unsigned long esid, unsigned long vsid,
- mm_context_t context)
+static inline void __ste_allocate(unsigned long esid, unsigned long vsid)
{
unsigned char stab_entry;
unsigned long *offset;
@@ -186,7 +185,7 @@
}
esid = GET_ESID(ea);
- __ste_allocate(esid, vsid, context);
+ __ste_allocate(esid, vsid);
/* Order update */
asm volatile("sync":::"memory");
@@ -216,7 +215,7 @@
if (!IS_VALID_EA(pc) || (REGION_ID(pc) >= KERNEL_REGION_ID))
return;
vsid = get_vsid(mm->context, pc);
- __ste_allocate(pc_esid, vsid, mm->context);
+ __ste_allocate(pc_esid, vsid);
if (pc_esid == stack_esid)
return;
@@ -224,7 +223,7 @@
if (!IS_VALID_EA(stack) || (REGION_ID(stack) >= KERNEL_REGION_ID))
return;
vsid = get_vsid(mm->context, stack);
- __ste_allocate(stack_esid, vsid, mm->context);
+ __ste_allocate(stack_esid, vsid);
if (pc_esid == unmapped_base_esid || stack_esid == unmapped_base_esid)
return;
@@ -233,7 +232,7 @@
(REGION_ID(unmapped_base) >= KERNEL_REGION_ID))
return;
vsid = get_vsid(mm->context, unmapped_base);
- __ste_allocate(unmapped_base_esid, vsid, mm->context);
+ __ste_allocate(unmapped_base_esid, vsid);
/* Order update */
asm volatile("sync" : : : "memory");
--
David Gibson | For every complex problem there is a
david AT gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
reply other threads:[~2004-02-02 6:13 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=20040202060332.GA17234@zax \
--to=david@gibson.dropbear.id.au \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.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.