linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: akpm@linux-foundation.org
Cc: mgorman@suse.de, linux-mm@kvack.org, mhocko@suse.com,
	Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH] mm: Remove ancient/ambiguous comment
Date: Fri, 23 Jun 2017 14:35:17 +0300	[thread overview]
Message-ID: <1498217717-20945-1-git-send-email-nborisov@suse.com> (raw)

Currently pg_data_t is just a struct which describes a NUMA node memory 
layout. Let's keep the comment simple and remove ambiguity.

Signed-off-by: Nikolay Borisov <nborisov@suse.com>
---
 include/linux/mmzone.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index ef6a13b7bd3e..c870c65fb945 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -587,10 +587,6 @@ extern struct page *mem_map;
 #endif
 
 /*
- * The pg_data_t structure is used in machines with CONFIG_DISCONTIGMEM
- * (mostly NUMA machines?) to denote a higher-level memory zone than the
- * zone denotes.
- *
  * On NUMA machines, each NUMA node would have a pg_data_t to describe
  * it's memory layout.
  *
-- 
2.7.4

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2017-06-23 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 11:35 Nikolay Borisov [this message]
2017-06-23 11:46 ` Michal Hocko
2017-06-23 12:08   ` [PATCH v2] " Nikolay Borisov
2017-06-23 12:14     ` Michal Hocko
2017-06-23 12:22 ` [PATCHi v3] " Nikolay Borisov

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=1498217717-20945-1-git-send-email-nborisov@suse.com \
    --to=nborisov@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.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