All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Cong Wang <amwang@redhat.com>,
	David Howells <dhowells@redhat.com>
Subject: [PATCH 04/12] frv: remove km_type definitions
Date: Sat, 23 Jun 2012 18:04:15 +0800	[thread overview]
Message-ID: <1340445863-16111-5-git-send-email-amwang@redhat.com> (raw)
In-Reply-To: <1340445863-16111-1-git-send-email-amwang@redhat.com>

Signed-off-by: Cong Wang <amwang@redhat.com>
---
 arch/frv/include/asm/kmap_types.h |   24 +-----------------------
 1 files changed, 1 insertions(+), 23 deletions(-)

diff --git a/arch/frv/include/asm/kmap_types.h b/arch/frv/include/asm/kmap_types.h
index f8e16b2..43901f2 100644
--- a/arch/frv/include/asm/kmap_types.h
+++ b/arch/frv/include/asm/kmap_types.h
@@ -2,28 +2,6 @@
 #ifndef _ASM_KMAP_TYPES_H
 #define _ASM_KMAP_TYPES_H
 
-enum km_type {
-	/* arch specific kmaps - change the numbers attached to these at your peril */
-	__KM_CACHE,		/* cache flush page attachment point */
-	__KM_PGD,		/* current page directory */
-	__KM_ITLB_PTD,		/* current instruction TLB miss page table lookup */
-	__KM_DTLB_PTD,		/* current data TLB miss page table lookup */
-
-	/* general kmaps */
-        KM_BOUNCE_READ,
-        KM_SKB_SUNRPC_DATA,
-        KM_SKB_DATA_SOFTIRQ,
-        KM_USER0,
-        KM_USER1,
-	KM_BIO_SRC_IRQ,
-	KM_BIO_DST_IRQ,
-	KM_PTE0,
-	KM_PTE1,
-	KM_IRQ0,
-	KM_IRQ1,
-	KM_SOFTIRQ0,
-	KM_SOFTIRQ1,
-	KM_TYPE_NR
-};
+#define KM_TYPE_NR 17
 
 #endif
-- 
1.7.7.6


  parent reply	other threads:[~2012-06-23 10:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23 10:04 [PATCH 00/12] kmap_atomic cleanup for 3.6 Cong Wang
2012-06-23 10:04 ` [PATCH 01/12] jbd2: remove the second argument of kmap_atomic Cong Wang
2012-06-23 10:04 ` [PATCH 02/12] arm: remove km_type definitions Cong Wang
2012-06-23 10:04   ` Cong Wang
2012-06-23 10:04 ` [PATCH 03/12] powerpc: " Cong Wang
2012-06-23 10:04   ` Cong Wang
2012-06-23 10:04 ` Cong Wang [this message]
2012-06-26 20:25   ` [PATCH 04/12] frv: " Geert Uytterhoeven
2012-06-27  3:24     ` Cong Wang
2012-06-27  7:32       ` Geert Uytterhoeven
2012-06-23 10:04 ` [PATCH 05/12] avr32: " Cong Wang
2012-06-26  7:28   ` Hans-Christian Egtvedt
2012-06-23 10:04 ` [PATCH 06/12] asm-generic: " Cong Wang
2012-06-23 10:04 ` [uml-devel] [PATCH 07/12] um: " Cong Wang
2012-06-23 10:04   ` Cong Wang
2012-06-23 10:04 ` [PATCH 08/12] tile: " Cong Wang
2012-06-26 17:48   ` Chris Metcalf
2012-06-23 10:04 ` [PATCH 09/12] highmem: remove the deprecated form of kmap_atomic Cong Wang
2012-06-23 10:04 ` [PATCH 10/12] feature-removal-schedule.txt: remove kmap_atomic(page, km_type) Cong Wang
2012-06-23 10:04 ` [PATCH 11/12] vmalloc: remove KM_USER0 from comments Cong Wang
2012-06-23 10:04   ` Cong Wang
2012-06-23 10:04 ` [PATCH 12/12] pipe: " Cong Wang
2012-06-23 21:11 ` [PATCH 00/12] kmap_atomic cleanup for 3.6 Arnd Bergmann
2012-06-25  4:26   ` Cong Wang
2012-06-25 15:18     ` Arnd Bergmann
2012-06-25 17:35       ` Peter Zijlstra
2012-06-25 20:43         ` Arnd Bergmann
2012-06-26  8:17           ` Peter Zijlstra
2012-06-26 11:49             ` Cong Wang

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=1340445863-16111-5-git-send-email-amwang@redhat.com \
    --to=amwang@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.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.