All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 00/12] kmap_atomic cleanup for 3.6
Date: Mon, 25 Jun 2012 12:26:22 +0800	[thread overview]
Message-ID: <1340598382.19173.3.camel@cr0> (raw)
In-Reply-To: <201206232111.25411.arnd@arndb.de>

On Sat, 2012-06-23 at 21:11 +0000, Arnd Bergmann wrote:
> On Saturday 23 June 2012, Cong Wang wrote:
> > After few releases, it seems there are no more callers
> > using the deprecated form of kmap_atomic(), the one
> > with two parameters. So we can remove it now and remove
> > the KM_* definition except KM_TYPE_NR together.
> > 
> > All the patches are available at:
> > 
> >         git://github.com/congwang/linux.git #kmap_atomic
> > 
> 
> What is the significance of having an architecture-specific
> definition for KM_TYPE_NR now? Should that be replaced
> with a fixed value in include/linux/highmem.h so we can
> remove the asm/kmap_types.h files entirely?
> 

Different arch has different values for KM_TYPE_NR, I am not sure if
unifying them to a fixed value could fit all? For safety, I kept their
original values.

Thanks.


  reply	other threads:[~2012-06-25  4:26 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 ` [PATCH 04/12] frv: " Cong Wang
2012-06-26 20:25   ` 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 [this message]
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=1340598382.19173.3.camel@cr0 \
    --to=amwang@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --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.