From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Joey Pabalinas <joeypabalinas@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-mm@kvack.org, Brian Cain <bcain@kernel.org>,
Kees Cook <kees@kernel.org>
Subject: Re: [PATCH 0/2] change "a mm_struct" to "an mm_struct" in comment
Date: Thu, 4 Sep 2025 11:52:00 +0100 [thread overview]
Message-ID: <3f5dff1c-06da-44dd-b5f6-053826152941@lucifer.local> (raw)
In-Reply-To: <247f1fb3-6966-4789-8f26-7d4126318c5f@lucifer.local>
On Thu, Sep 04, 2025 at 11:46:52AM +0100, Lorenzo Stoakes wrote:
> isn't great RoI on the churcn here. It is also very silly to make this two
Oops typo - should be "isn't great RoI on the _churn_ here" :)
prev parent reply other threads:[~2025-09-04 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 6:23 Joey Pabalinas
2025-09-04 6:23 ` [PATCH 1/2] Hexagon: " Joey Pabalinas
2025-09-04 6:23 ` [PATCH 2/2] fork: " Joey Pabalinas
2025-09-04 10:46 ` [PATCH 0/2] " Lorenzo Stoakes
2025-09-04 10:52 ` Lorenzo Stoakes [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=3f5dff1c-06da-44dd-b5f6-053826152941@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=bcain@kernel.org \
--cc=joeypabalinas@gmail.com \
--cc=kees@kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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