From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: nfont@linux.vnet.ibm.com, mwb@linux.vnet.ibm.com,
Bharata B Rao <bharata@linux.vnet.ibm.com>
Subject: [RFC PATCH v0 0/2] ibm,dynamic-memory-v2 fix
Date: Wed, 21 Feb 2018 16:06:25 +0530 [thread overview]
Message-ID: <1519209387-29767-1-git-send-email-bharata@linux.vnet.ibm.com> (raw)
Patch 1 fixes a bug that results in unexpected flag bit in
ibm,dynamic-memory-v2 DT property and wrong number of entries
getting created in the same property during hotplug.
Patch 2 can be optionally considered. It renames DRMEM_LMB_RESERVED
to DRMEM_LMB_ISOLATED. May be it could be renamed to even more
appropriate name.
Bharata B Rao (2):
powerpc,drmem: Fix unexpected flag value in ibm,dynamic-memory-v2
powerpc,drmem: Rename DRMEM_LMB_RESERVED to DRMEM_LMB_ISOLATED
arch/powerpc/include/asm/drmem.h | 14 ++++-----
arch/powerpc/mm/drmem.c | 8 ++---
arch/powerpc/platforms/pseries/hotplug-memory.c | 40 ++++++++++++-------------
3 files changed, 31 insertions(+), 31 deletions(-)
--
2.7.4
next reply other threads:[~2018-02-21 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 10:36 Bharata B Rao [this message]
2018-02-21 10:36 ` [RFC PATCH v0 1/2] powerpc, drmem: Fix unexpected flag value in ibm, dynamic-memory-v2 Bharata B Rao
2018-02-21 11:48 ` Michael Ellerman
2018-02-21 13:36 ` Bharata B Rao
2018-02-22 13:51 ` Nathan Fontenot
2018-02-26 5:35 ` [RFC, v0, " Michael Ellerman
2018-02-21 10:36 ` [RFC PATCH v0 2/2] powerpc, drmem: Rename DRMEM_LMB_RESERVED to DRMEM_LMB_ISOLATED Bharata B Rao
2018-02-22 13:52 ` Nathan Fontenot
2022-03-11 17:09 ` Christophe Leroy
2018-02-21 12:27 ` [RFC PATCH v0 0/2] ibm,dynamic-memory-v2 fix Balbir Singh
2018-02-21 13:41 ` Bharata B Rao
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=1519209387-29767-1-git-send-email-bharata@linux.vnet.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mwb@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.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).