All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Zhao Hongjiang <zhaohongjiang@huawei.com>
Cc: linux-parisc@vger.kernel.org
Subject: Re: [PATCH] parisc: remove the second argument of kmap_atomic
Date: Sun, 28 Apr 2013 21:56:39 +0200	[thread overview]
Message-ID: <517D7EF7.1080702@gmx.de> (raw)
In-Reply-To: <517BAB83.2060308@huawei.com>

On 04/27/2013 12:42 PM, Zhao Hongjiang wrote:
> kmap_atomic allows only one argument now, just move the second.
> 
> Signed-off-by: Zhao Hongjiang <zhaohongjiang@huawei.com>

Thanks!
Queued up in parisc tree for 3.10.

Helge


> ---
>  arch/parisc/kernel/cache.c |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/parisc/kernel/cache.c b/arch/parisc/kernel/cache.c
> index 4b12890..6df734a 100644
> --- a/arch/parisc/kernel/cache.c
> +++ b/arch/parisc/kernel/cache.c
> @@ -609,7 +609,7 @@ void clear_user_highpage(struct page *page, unsigned long vaddr)
>  	/* Clear using TMPALIAS region.  The page doesn't need to
>  	   be flushed but the kernel mapping needs to be purged.  */
>  
> -	vto = kmap_atomic(page, KM_USER0);
> +	vto = kmap_atomic(page);
>  
>  	/* The PA-RISC 2.0 Architecture book states on page F-6:
>  	   "Before a write-capable translation is enabled, *all*
> @@ -644,8 +644,8 @@ void copy_user_highpage(struct page *to, struct page *from,
>  	   the `to' page must be flushed in copy_user_page_asm since
>  	   it can be used to bring in executable code.  */
>  
> -	vfrom = kmap_atomic(from, KM_USER0);
> -	vto = kmap_atomic(to, KM_USER1);
> +	vfrom = kmap_atomic(from);
> +	vto = kmap_atomic(to);
>  
>  	purge_kernel_dcache_page_asm((unsigned long)vto);
>  	purge_tlb_start(flags);
> 


      parent reply	other threads:[~2013-04-28 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27 10:42 [PATCH] parisc: remove the second argument of kmap_atomic Zhao Hongjiang
2013-04-27 11:43 ` Rolf Eike Beer
2013-04-28  1:05   ` Zhao Hongjiang
2013-04-28 19:56 ` Helge Deller [this message]

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=517D7EF7.1080702@gmx.de \
    --to=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.org \
    --cc=zhaohongjiang@huawei.com \
    /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.