From: Keith Packard <keithp@keithp.com>
Date: Tue, 24 Jun 2008 05:03:06 +0000 (-0700)
Subject: drm_compat: it's CONFIG_HIGHMEM, not CONFIG_HIMEM
X-Git-Tag: submit/1.0/20121108.012404~757^2~33
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=c0043155ad7199835d631e3daed5c641642c314e;p=profile%2Fivi%2Flibdrm.git

drm_compat: it's CONFIG_HIGHMEM, not CONFIG_HIMEM

A mis-spelled config option (was it spelled that way in the past?)
eliminated kmap_atomic_prot_pfn from core DRM.
---

diff --git a/linux-core/drm_compat.h b/linux-core/drm_compat.h
index 30834f3..6aa19c5 100644
--- a/linux-core/drm_compat.h
+++ b/linux-core/drm_compat.h
@@ -329,7 +329,7 @@ typedef _Bool                   bool;
 #endif
 
 
-#if (defined(CONFIG_X86) && defined(CONFIG_X86_32) && defined(CONFIG_HIMEM))
+#if (defined(CONFIG_X86) && defined(CONFIG_X86_32) && defined(CONFIG_HIGHMEM))
 #define DRM_KMAP_ATOMIC_PROT_PFN
 extern void *kmap_atomic_prot_pfn(unsigned long pfn, enum km_type type,
 				  pgprot_t protection);