linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ritesh.harjani@gmail.com (ritesh.harjani at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] arm64: tlbflush.h: Clean up comment
Date: Wed, 21 May 2014 09:43:20 +0530	[thread overview]
Message-ID: <1400645600-35973-2-git-send-email-ritesh.harjani@gmail.com> (raw)
In-Reply-To: <1400645600-35973-1-git-send-email-ritesh.harjani@gmail.com>

From: Ritesh Harjani <ritesh.harjani@gmail.com>

Clean up the undefined function name(flush_kern_tlb_page)
from the comment in tlbflush.h

Signed-off-by: Ritesh Harjani <ritesh.harjani@gmail.com>
---
 arch/arm64/include/asm/tlbflush.h | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/arch/arm64/include/asm/tlbflush.h b/arch/arm64/include/asm/tlbflush.h
index 8b48203..85e4f98 100644
--- a/arch/arm64/include/asm/tlbflush.h
+++ b/arch/arm64/include/asm/tlbflush.h
@@ -63,12 +63,6 @@ extern struct cpu_tlb_fns cpu_tlb;
  *		- vaddr - virtual address (may not be aligned)
  *		- vma	- vma_struct describing address range
  *
- *	flush_kern_tlb_page(kaddr)
- *
- *		Invalidate the TLB entry for the specified page.  The address
- *		will be in the kernels virtual memory space.  Current uses
- *		only require the D-TLB to be invalidated.
- *		- kaddr - Kernel virtual memory address
  */
 static inline void flush_tlb_all(void)
 {
-- 
1.8.1.3

  reply	other threads:[~2014-05-21  4:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21  4:13 [PATCH 0/1] Clean up the unused comments from arm64 tlbflush.h ritesh.harjani at gmail.com
2014-05-21  4:13 ` ritesh.harjani at gmail.com [this message]
2014-05-21  4:22   ` [PATCH 1/1] arm64: tlbflush.h: Clean up comment Arun KS
2014-05-21  5:38     ` Ritesh Harjani

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=1400645600-35973-2-git-send-email-ritesh.harjani@gmail.com \
    --to=ritesh.harjani@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).