From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
maple-tree@lists.infradead.org, linux-mm@kvack.org
Subject: Re: [PATCH] maple_tree: fix typos/spellos etc.
Date: Sun, 10 Dec 2023 15:53:57 -0800 [thread overview]
Message-ID: <f4a56419-088f-42e7-bf50-4afbe7c8f571@infradead.org> (raw)
In-Reply-To: <20231210145601.177b543ca2ed28b9551575ff@linux-foundation.org>
On 12/10/23 14:56, Andrew Morton wrote:
> On Sun, 10 Dec 2023 21:13:15 +0000 Matthew Wilcox <willy@infradead.org> wrote:
>
>> On Sat, Dec 09, 2023 at 10:38:39PM -0800, Randy Dunlap wrote:
>>> - * mas_topiary_node() - Dispose of a singe node
>>> + * mas_topiary_node() - Dispose of a single node
>>
>> That's all well and good, but how do we dispose of singed nodes now?
>
> Lol, this is my all-time favorite typo!
>
>
> hp2:/usr/src/mm> git log | grep Singed-off-by | wc -l
> 59
>
> (sounds painful)
>
> hp2:/usr/src/linux-6.7-rc4> grep -ri singe .
>
Current linux-next shows:
$ git grep -iw singe
arch/x86/events/intel/pt.c: * In case of singe-entry ToPA, always put the self-referencing END
arch/x86/kvm/vmx/vmx.c: * evmcs in singe VM shares same assist page.
drivers/input/misc/yealink.c: /* Combine up to <len> consecutive LCD bytes in a singe request
drivers/net/ethernet/brocade/bna/bfa_defs_status.h: * NOTE: The error msgs are auto generated from the comments. Only singe line
kernel/trace/trace_events_filter.c: * struct prog_entry - a singe entry in the filter program
lib/maple_tree.c: * mas_topiary_node() - Dispose of a singe node
lib/maple_tree.c: /* New root needs a singe node */
sound/core/seq/seq_queue.c:/* enqueue a event to singe queue */
sound/pci/rme9652/hdspm.c: /* Changing between Singe, Double and Quad speed is not
but there is also "unsinged", "assinged", & "singel" if the -w is omitted.
And somehow the two Chinese translations of submitting-patches.rst contain
Singed-off-by.
--
#Randy
https://people.kernel.org/tglx/notes-about-netiquette
https://subspace.kernel.org/etiquette.html
next prev parent reply other threads:[~2023-12-10 23:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 6:38 Randy Dunlap
2023-12-10 21:13 ` Matthew Wilcox
2023-12-10 21:32 ` Randy Dunlap
2023-12-10 22:56 ` Andrew Morton
2023-12-10 23:53 ` Randy Dunlap [this message]
2023-12-11 15:18 ` Liam R. Howlett
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=f4a56419-088f-42e7-bf50-4afbe7c8f571@infradead.org \
--to=rdunlap@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=willy@infradead.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