The patch titled
     m68knommu: use TRHEAD_SIZE instead of hard constant
has been added to the -mm tree.  Its filename is
     m68knommu-use-trhead_size-instead-of-hard-constant.patch

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this

------------------------------------------------------
Subject: m68knommu: use TRHEAD_SIZE instead of hard constant
From: Greg Ungerer <[EMAIL PROTECTED]>

Use THREAD_SIZE instead of a hard constant.

Signed-off-by: Philippe De Muyter <[EMAIL PROTECTED]>
Signed-off-by: Greg Ungerer <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 arch/m68knommu/kernel/process.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN 
arch/m68knommu/kernel/process.c~m68knommu-use-trhead_size-instead-of-hard-constant
 arch/m68knommu/kernel/process.c
--- 
a/arch/m68knommu/kernel/process.c~m68knommu-use-trhead_size-instead-of-hard-constant
+++ a/arch/m68knommu/kernel/process.c
@@ -377,7 +377,7 @@ unsigned long get_wchan(struct task_stru
        fp = ((struct switch_stack *)p->thread.ksp)->a6;
        do {
                if (fp < stack_page+sizeof(struct thread_info) ||
-                   fp >= 8184+stack_page)
+                   fp >= THREAD_SIZE-8+stack_page)
                        return 0;
                pc = ((unsigned long *)fp)[1];
                if (!in_sched_functions(pc))
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

drivers-mtd-maps-nettelc-possible-cleanups.patch
m68knommu-fix-coldfire-timer-off-by-1.patch
nommu-stub-expand_stack-for-nommu-case.patch
m68knommu-use-trhead_size-instead-of-hard-constant.patch
m68knommu-remove-cruft-from-setup-code.patch
m68knommu-remove-old-cache-management-cruft-from-mm-code.patch
nommu-report-correct-errno-in-message.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to