The patch titled
     time-x86_64-re-enable-vsyscall-support-for-x86_64-tidy
has been removed from the -mm tree.  Its filename was
     time-x86_64-re-enable-vsyscall-support-for-x86_64-tidy.patch

This patch was dropped because it was folded into 
time-x86_64-re-enable-vsyscall-support-for-x86_64.patch

------------------------------------------------------
Subject: time-x86_64-re-enable-vsyscall-support-for-x86_64-tidy
From: Andrew Morton <[EMAIL PROTECTED]>

Cc: John Stultz <[EMAIL PROTECTED]>
Cc: Ingo Molnar <[EMAIL PROTECTED]>
Cc: Thomas Gleixner <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
Cc: Roman Zippel <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 arch/x86_64/kernel/hpet.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6.20-rc6-mm/arch/x86_64/kernel/hpet.c
===================================================================
--- linux-2.6.20-rc6-mm.orig/arch/x86_64/kernel/hpet.c
+++ linux-2.6.20-rc6-mm/arch/x86_64/kernel/hpet.c
@@ -460,7 +460,7 @@ static cycle_t read_hpet(void)
 
 static cycle_t __vsyscall_fn vread_hpet(void)
 {
-       return (cycle_t)readl((void *)fix_to_virt(VSYSCALL_HPET) + 0xf0);
+       return readl((void __iomem *)fix_to_virt(VSYSCALL_HPET) + 0xf0);
 }
 
 struct clocksource clocksource_hpet = {

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

origin.patch
vmi-versus-hrtimers.patch
add-a-functions-to-handle-interrupt-affinity-setting.patch
i386-use-gtod-persistent-clock-support.patch
hrtimers-namespace-and-enum-cleanup.patch
hrtimers-cleanup-locking.patch
hrtimers-add-state-tracking.patch
clockevents-i383-drivers.patch
generic-vsyscall-gtod-support-for-generic_time.patch
time-x86_64-split-x86_64-kernel-timec-up.patch
time-x86_64-convert-x86_64-to-use-generic_time.patch
time-x86_64-re-enable-vsyscall-support-for-x86_64.patch
time-x86_64-re-enable-vsyscall-support-for-x86_64-tidy.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