From: Michael Ellerman <mpe@ellerman•id.au>
To: Nathan Fontenot <nfont@linux•vnet.ibm.com>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [1/2] powerpc/pseries: Move property cloning into its own routine
Date: Sun, 17 Jul 2016 20:28:20 +1000 (AEST) [thread overview]
Message-ID: <3rsjFJ4Lydz9t0G@ozlabs.org> (raw)
In-Reply-To: <5767F707.3050707@linux.vnet.ibm.com>
On Mon, 2016-20-06 at 14:00:39 UTC, Nathan Fontenot wrote:
> Move property cloning code into its own routine
>
> Split the pieces of dlpar_clone_drconf_property() that create a copy of
> the property struct into its own routine. This allows for creating
> clones of more than just the ibm,dynamic-memory property used in memory
> hotplug.
>
> Signed-off-by: Nathan Fontenot <nfont@linux•vnet.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/c2101c9039fe2a005f7b4138e0
cheers
next prev parent reply other threads:[~2016-07-17 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 13:58 [PATCH 0/2] powerpc/pseries: Dynamic associativity-lookup-arrays updating Nathan Fontenot
2016-06-20 14:00 ` [PATCH 1/2] powerpc/pseries: Move property cloning into its own routine Nathan Fontenot
2016-07-17 10:28 ` Michael Ellerman [this message]
2016-06-20 14:01 ` [PATCH 2/2] powerpc/pseries: Dynamic add entires to associativity lookup array Nathan Fontenot
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=3rsjFJ4Lydz9t0G@ozlabs.org \
--to=mpe@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=nfont@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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