public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hyuk Myeong" <hyuk.myeong@lge.com>
To: <linux@arm.linux.org.uk>, <akpm@linux-foundation.org>,
	<kirill.shutemov@linux.intel.com>, <steve.capper@linaro.org>,
	<catalin.marinas@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH] ARM: pgtable: Fix typo in the comment
Date: Tue, 9 Jun 2015 15:52:47 +0900	[thread overview]
Message-ID: <024f01d0a280$e561f460$b025dd20$@lge.com> (raw)

This patch fix a spelling typo in the comment in pgtable-2level.h.

Signed-off-by: Hyuk Myeong <hyuk.myeong@lge.com>
---
 arch/arm/include/asm/pgtable-2level.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/include/asm/pgtable-2level.h
b/arch/arm/include/asm/pgtable-2level.h
index bfd662e..49f91be 100644
--- a/arch/arm/include/asm/pgtable-2level.h
+++ b/arch/arm/include/asm/pgtable-2level.h
@@ -66,7 +66,7 @@
  *
  * However, when the "young" bit is cleared, we deny access to the page
  * by clearing the hardware PTE.  Currently Linux does not flush the TLB
- * for us in this case, which means the TLB will retain the transation
+ * for us in this case, which means the TLB will retain the transaction
  * until either the TLB entry is evicted under pressure, or a context
  * switch which changes the user space mapping occurs.
  */
--
1.9.3


             reply	other threads:[~2015-06-09  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  6:52 Hyuk Myeong [this message]
2015-06-09  8:42 ` [PATCH] ARM: pgtable: Fix typo in the comment Steve Capper
2015-06-10  2:33   ` Hyuk Myeong
  -- strict thread matches above, loose matches on Subject: below --
2015-09-11 11:22 Hyuk Myeong

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='024f01d0a280$e561f460$b025dd20$@lge.com' \
    --to=hyuk.myeong@lge.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=steve.capper@linaro.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