From: Jonathan Corbet <corbet@lwn.net>
To: I Hsin Cheng <richard120310@gmail.com>
Cc: akpm@linux-foundation.org, jserv@ccns.ncku.edu.tw,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
I Hsin Cheng <richard120310@gmail.com>
Subject: Re: [PATCH] docs/mm: Physical memory: Remove zone_t
Date: Thu, 16 Jan 2025 11:17:03 -0700 [thread overview]
Message-ID: <87r052zkrk.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250115070355.41769-1-richard120310@gmail.com>
I Hsin Cheng <richard120310@gmail.com> writes:
> "zone_t" doesn't exist in current code base anymore, remove the
> description of it.
>
> Signed-off-by: I Hsin Cheng <richard120310@gmail.com>
> ---
> Documentation/mm/physical_memory.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/mm/physical_memory.rst b/Documentation/mm/physical_memory.rst
> index 531e73b00..71fd4a6ac 100644
> --- a/Documentation/mm/physical_memory.rst
> +++ b/Documentation/mm/physical_memory.rst
> @@ -33,7 +33,7 @@ The entire physical address space is partitioned into one or more blocks
> called zones which represent ranges within memory. These ranges are usually
> determined by architectural constraints for accessing the physical memory.
> The memory range within a node that corresponds to a particular zone is
> -described by a ``struct zone``, typedeffed to ``zone_t``. Each zone has
> +described by a ``struct zone``. Each zone has
> one of the types described below.
Makes sense; applied, thanks.
jon
prev parent reply other threads:[~2025-01-16 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 7:03 I Hsin Cheng
2025-01-15 15:44 ` Randy Dunlap
2025-01-16 18:17 ` 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=87r052zkrk.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard120310@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
all inboxes | Powered by JetHome®