From: Balbir Singh <bsingharora@gmail.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [PATCH v2] powerpc/mm: Fix typo in set_pte_at()
Date: Wed, 8 Feb 2017 13:44:01 +0530 [thread overview]
Message-ID: <20170208081401.GB17068@localhost.localdomain> (raw)
In-Reply-To: <1486523810-21112-1-git-send-email-gwshan@linux.vnet.ibm.com>
On Wed, Feb 08, 2017 at 02:16:50PM +1100, Gavin Shan wrote:
> This fixes the typo about the _PAGE_PTE in set_pte_at() by changing
> "tryint" to "trying to".
>
> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
> ---
> v2: Removed "Fixes" tag
Not much to ack, but
Acked-by: Balbir Singh <bsingharora@gmail.com>
next prev parent reply other threads:[~2017-02-08 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 3:16 [PATCH v2] powerpc/mm: Fix typo in set_pte_at() Gavin Shan
2017-02-08 8:14 ` Balbir Singh [this message]
2017-02-19 11:33 ` [v2] " Michael Ellerman
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=20170208081401.GB17068@localhost.localdomain \
--to=bsingharora@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).