From: Jonathan Corbet <corbet@lwn.net>
To: Amos Wenger <amos@bearcove.net>, amos@bearcove.net
Cc: David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
"open list:MEMORY HOT(UN)PLUG" <linux-mm@kvack.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/memory-hotplug: fix typo in documentation
Date: Tue, 10 Oct 2023 13:12:21 -0600 [thread overview]
Message-ID: <87wmvu5m22.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231006112636.97128-1-amos@bearcove.net>
Amos Wenger <amos@bearcove.net> writes:
> I'm 90% sure memory hotunplugging doesn't involve a "fist" phase
>
> Signed-off-by: Amos Wenger <amos@bearcove.net>
> ---
> Documentation/admin-guide/mm/memory-hotplug.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Depends on how hard it is to get out, perhaps :)
Applied, thanks.
jon
prev parent reply other threads:[~2023-10-10 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 11:26 Amos Wenger
2023-10-06 11:46 ` David Hildenbrand
2023-10-10 19:12 ` Jonathan Corbet [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=87wmvu5m22.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=amos@bearcove.net \
--cc=david@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
/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