[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fd5018d6-4f38-42c8-95ac-ee9945489c56@infradead.org>
Date: Wed, 15 Jan 2025 07:44:46 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: I Hsin Cheng <richard120310@...il.com>, corbet@....net
Cc: akpm@...ux-foundation.org, jserv@...s.ncku.edu.tw,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs/mm: Physical memory: Remove zone_t
On 1/14/25 11:03 PM, I Hsin Cheng wrote:
> "zone_t" doesn't exist in current code base anymore, remove the
> description of it.
>
> Signed-off-by: I Hsin Cheng <richard120310@...il.com>
Reviewed-by: Randy Dunlap <rdunlap@...radead.org>
Thanks.
> ---
> 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.
>
> * ``ZONE_DMA`` and ``ZONE_DMA32`` historically represented memory suitable for
--
~Randy
Powered by blists - more mailing lists