From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Michael Bringmann <mwb@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
Thomas Falcon <tlfalcon@linux.vnet.ibm.com>,
Juliet Kim <minkim@us.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: [Internal Review PATCH] powerpc/pseries: Refactor code to centralize drmem feature
Date: Mon, 26 Nov 2018 14:36:47 -0600 [thread overview]
Message-ID: <20181126203633.11871.94010.stgit@ltczep4-lp5.aus.stglabs.ibm.com> (raw)
The implementation of the pseries-specific dynamic memory features
is currently implemented in several non-pseries-specific files.
This patch set moves the implementation of the device-tree parsing
code for the properties ibm,dynamic-memory, ibm,dynamic-memory-v2,
and its representation in the kernel into the platform-specific
directory to the Pseries features.
Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
Michael Bringmann (4):
powerpc/pseries: Relocate drmem.c to pseries
powerpc/pseries: Move DRMEM processing out of prom.c
powerpc/pseries: Move DRMEM processing out of numa.c
powerpc/pseries: Relocate drmem.h to pseries
next reply other threads:[~2018-11-26 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 20:36 Michael Bringmann [this message]
2018-11-26 20:37 ` [Internal Review PATCH] powerpc/pseries: Relocate drmem.c to pseries Michael Bringmann
2018-11-26 20:37 ` [Internal Review PATCH] powerpc/pseries: Move DRMEM processing out of prom.c Michael Bringmann
2018-11-26 20:37 ` [Internal Review PATCH] powerpc/pseries: Move DRMEM processing out of numa.c Michael Bringmann
2018-11-26 20:37 ` [Internal Review PATCH] powerpc/pseries: Relocate drmem.h to pseries Michael Bringmann
2018-11-27 20:28 ` [Internal Review PATCH] powerpc/pseries: Refactor code to centralize drmem feature Michael Bringmann
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=20181126203633.11871.94010.stgit@ltczep4-lp5.aus.stglabs.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=minkim@us.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=tlfalcon@linux.vnet.ibm.com \
--cc=tyreld@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).