From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,rdunlap@infradead.org,jserv@ccns.ncku.edu.tw,corbet@lwn.net,richard120310@gmail.com,akpm@linux-foundation.org
Subject: [merged] docs-mm-physical-memory-remove-zone_t.patch removed from -mm tree
Date: Thu, 16 Jan 2025 18:27:00 -0800 [thread overview]
Message-ID: <20250117022700.D3550C4CED6@smtp.kernel.org> (raw)
The quilt patch titled
Subject: docs/mm: physical memory: Remove zone_t
has been removed from the -mm tree. Its filename was
docs-mm-physical-memory-remove-zone_t.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: I Hsin Cheng <richard120310@gmail.com>
Subject: docs/mm: physical memory: Remove zone_t
Date: Wed, 15 Jan 2025 15:03:55 +0800
"zone_t" doesn't exist in current code base anymore, remove the
description of it.
Link: https://lkml.kernel.org/r/20250115070355.41769-1-richard120310@gmail.com
Signed-off-by: I Hsin Cheng <richard120310@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Ching-Chun (Jim) Huang <jserv@ccns.ncku.edu.tw>
Cc: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
Documentation/mm/physical_memory.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/Documentation/mm/physical_memory.rst~docs-mm-physical-memory-remove-zone_t
+++ a/Documentation/mm/physical_memory.rst
@@ -33,7 +33,7 @@ The entire physical address space is par
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
_
Patches currently in -mm which might be from richard120310@gmail.com are
reply other threads:[~2025-01-17 2:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250117022700.D3550C4CED6@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=jserv@ccns.ncku.edu.tw \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.