From: Seth Jennings <sjennings@variantweb.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Seth Jennings <sjennings@variantweb.net>,
Andrew Banman <abanman@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
Russ Anderson <rja@sgi.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] drivers: memory: rename remove_memory_block() to remove_memory_section()
Date: Wed, 2 Dec 2015 09:07:00 -0600 [thread overview]
Message-ID: <1449068821-9870-2-git-send-email-sjennings@variantweb.net> (raw)
In-Reply-To: <1449068821-9870-1-git-send-email-sjennings@variantweb.net>
The function removes a section, not a block. Rename to reflect
actual functionality.
Signed-off-by: Seth Jennings <sjennings@variantweb.net>
---
drivers/base/memory.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index ca2ce02..dd30744 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -688,7 +688,7 @@ unregister_memory(struct memory_block *memory)
device_unregister(&memory->dev);
}
-static int remove_memory_block(unsigned long node_id,
+static int remove_memory_section(unsigned long node_id,
struct mem_section *section, int phys_device)
{
struct memory_block *mem;
@@ -712,7 +712,7 @@ int unregister_memory_section(struct mem_section *section)
if (!present_section(section))
return -EINVAL;
- return remove_memory_block(0, section, 0);
+ return remove_memory_section(0, section, 0);
}
#endif /* CONFIG_MEMORY_HOTREMOVE */
--
2.5.0
next prev parent reply other threads:[~2015-12-02 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 15:06 [PATCH 1/3] drivers: memory: clean up section counting Seth Jennings
2015-12-02 15:07 ` Seth Jennings [this message]
2015-12-02 15:07 ` [PATCH 3/3] drivers: memory: prohibit offlining of memory blocks with missing sections Seth Jennings
2015-12-02 22:45 ` Andrew Morton
2015-12-03 17:58 ` [PATCH] drivers: memory: check for missing sections when testing zones Andrew Banman
2015-12-05 0:03 ` Andrew Morton
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=1449068821-9870-2-git-send-email-sjennings@variantweb.net \
--to=sjennings@variantweb.net \
--cc=abanman@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rja@sgi.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;
as well as URLs for NNTP newsgroup(s).