From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
npiggin@gmail.com, aneesh.kumar@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: mm: book3s64: Fix a typo in the file mmu_context.c
Date: Fri, 12 Mar 2021 08:41:26 -0800 [thread overview]
Message-ID: <7a2b6ee3-33cf-00a3-fb5c-f8bcf404f29c@infradead.org> (raw)
In-Reply-To: <20210312112537.4585-1-unixbhaskar@gmail.com>
On 3/12/21 3:25 AM, Bhaskar Chowdhury wrote:
>
> s/detalis/details/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> arch/powerpc/mm/book3s64/mmu_context.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/mm/book3s64/mmu_context.c b/arch/powerpc/mm/book3s64/mmu_context.c
> index 0c8557220ae2..c10fc8a72fb3 100644
> --- a/arch/powerpc/mm/book3s64/mmu_context.c
> +++ b/arch/powerpc/mm/book3s64/mmu_context.c
> @@ -119,7 +119,7 @@ static int hash__init_new_context(struct mm_struct *mm)
> /* This is fork. Copy hash_context details from current->mm */
> memcpy(mm->context.hash_context, current->mm->context.hash_context, sizeof(struct hash_mm_context));
> #ifdef CONFIG_PPC_SUBPAGE_PROT
> - /* inherit subpage prot detalis if we have one. */
> + /* inherit subpage prot details if we have one. */
> if (current->mm->context.hash_context->spt) {
> mm->context.hash_context->spt = kmalloc(sizeof(struct subpage_prot_table),
> GFP_KERNEL);
> --
--
~Randy
next prev parent reply other threads:[~2021-03-12 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 11:25 [PATCH] powerpc: mm: book3s64: Fix a typo in the file mmu_context.c Bhaskar Chowdhury
2021-03-12 16:41 ` Randy Dunlap [this message]
2021-03-31 1:09 ` 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=7a2b6ee3-33cf-00a3-fb5c-f8bcf404f29c@infradead.org \
--to=rdunlap@infradead.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=unixbhaskar@gmail.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 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).