From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 5/5] tools/testing: fix typo "mergable" in comment
Date: Fri, 4 Sep 2026 12:37:11 +0100 [thread overview]
Message-ID: <apqtOmwcvDaA8cp9@gremlin> (raw)
In-Reply-To: <20260904104854.25272-6-hemanth.selam@gmail.com>
On Fri, Sep 04, 2026 at 04:18:50PM +0530, Hemanth Selam wrote:
> Correct "mergable" to "mergeable", reported by scripts/checkpatch.pl using
> the misspelling list in scripts/spelling.txt. Only touches comments, no
> code changes.
>
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
This one I'd drop, as a series of mine I'm going to send soon removes it from
the kernel altogether, and I don't want conflicts on a typo fix :)
Thanks!
> ---
> tools/testing/vma/include/dup.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/vma/include/dup.h b/tools/testing/vma/include/dup.h
> index 4c58487b764e..302a6774fca5 100644
> --- a/tools/testing/vma/include/dup.h
> +++ b/tools/testing/vma/include/dup.h
> @@ -353,7 +353,7 @@ enum {
> #define VMA_ACCESS_FLAGS mk_vma_flags(VMA_READ_BIT, VMA_WRITE_BIT, VMA_EXEC_BIT)
>
> /*
> - * Special vmas that are non-mergable, non-mlock()able.
> + * Special vmas that are non-mergeable, non-mlock()able.
> */
> #define VM_SPECIAL (VM_IO | VM_DONTEXPAND | VM_PFNMAP | VM_MIXEDMAP)
>
> --
> 2.48.1
>
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-09-04 11:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260904104854.25272-1-hemanth.selam@gmail.com>
2026-09-04 10:48 ` [PATCH 1/5] asm-generic: fix typo "explicity" in comment Hemanth Selam
2026-09-04 11:33 ` Lorenzo Stoakes (ARM)
2026-09-04 21:58 ` Randy Dunlap
2026-09-04 23:59 ` SJ Park
2026-09-04 10:48 ` [PATCH 2/5] char: fix typo "funcion" " Hemanth Selam
2026-09-04 11:34 ` Lorenzo Stoakes (ARM)
2026-09-04 10:48 ` [PATCH 4/5] mm: fix typo "mergable" " Hemanth Selam
2026-09-04 11:35 ` Lorenzo Stoakes (ARM)
2026-09-04 10:48 ` [PATCH 5/5] tools/testing: " Hemanth Selam
2026-09-04 11:37 ` Lorenzo Stoakes (ARM) [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=apqtOmwcvDaA8cp9@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hemanth.selam@gmail.com \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pfalcato@suse.de \
--cc=vbabka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox