All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Jiri Kosina <trivial@kernel.org>,
	linux390@de.ibm.com, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH trivial] s390/mm: s/specifiation/specification/, s/an specification/a specification/
Date: Thu, 21 May 2015 14:27:39 +0200	[thread overview]
Message-ID: <20150521122739.GC4079@osiris> (raw)
In-Reply-To: <1432209647-20668-1-git-send-email-geert+renesas@glider.be>

On Thu, May 21, 2015 at 02:00:47PM +0200, Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
>  arch/s390/include/asm/pgtable.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/s390/include/asm/pgtable.h b/arch/s390/include/asm/pgtable.h
> index fc642399b489d896..9a04717f5d0cf40f 100644
> --- a/arch/s390/include/asm/pgtable.h
> +++ b/arch/s390/include/asm/pgtable.h
> @@ -1565,9 +1565,9 @@ static inline int has_transparent_hugepage(void)
>  /*
>   * 64 bit swap entry format:
>   * A page-table entry has some bits we have to treat in a special way.
> - * Bits 52 and bit 55 have to be zero, otherwise an specification
> + * Bits 52 and bit 55 have to be zero, otherwise a specification
>   * exception will occur instead of a page translation exception. The
> - * specifiation exception has the bad habit not to store necessary
> + * specification exception has the bad habit not to store necessary

Applied, thanks.

      reply	other threads:[~2015-05-21 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 12:00 [PATCH trivial] s390/mm: s/specifiation/specification/, s/an specification/a specification/ Geert Uytterhoeven
2015-05-21 12:27 ` Heiko Carstens [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=20150521122739.GC4079@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux390@de.ibm.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=trivial@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.