* [PATCH] docs/mm: Physical memory: Remove zone_t
@ 2025-01-15 7:03 I Hsin Cheng
2025-01-15 15:44 ` Randy Dunlap
2025-01-16 18:17 ` Jonathan Corbet
0 siblings, 2 replies; 3+ messages in thread
From: I Hsin Cheng @ 2025-01-15 7:03 UTC (permalink / raw)
To: corbet; +Cc: akpm, jserv, linux-doc, linux-kernel, I Hsin Cheng
"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.
* ``ZONE_DMA`` and ``ZONE_DMA32`` historically represented memory suitable for
--
2.43.0
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] docs/mm: Physical memory: Remove zone_t
2025-01-15 7:03 [PATCH] docs/mm: Physical memory: Remove zone_t I Hsin Cheng
@ 2025-01-15 15:44 ` Randy Dunlap
2025-01-16 18:17 ` Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2025-01-15 15:44 UTC (permalink / raw)
To: I Hsin Cheng, corbet; +Cc: akpm, jserv, linux-doc, linux-kernel
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@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] docs/mm: Physical memory: Remove zone_t
2025-01-15 7:03 [PATCH] docs/mm: Physical memory: Remove zone_t I Hsin Cheng
2025-01-15 15:44 ` Randy Dunlap
@ 2025-01-16 18:17 ` Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2025-01-16 18:17 UTC (permalink / raw)
To: I Hsin Cheng; +Cc: akpm, jserv, linux-doc, linux-kernel, I Hsin Cheng
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-01-16 18:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-01-15 7:03 [PATCH] docs/mm: Physical memory: Remove zone_t I Hsin Cheng
2025-01-15 15:44 ` Randy Dunlap
2025-01-16 18:17 ` Jonathan Corbet
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®