linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Nathan Fontenot <nfont@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org,
	Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH 1/4] powerpc: Make a bunch of things static
Date: Wed, 17 Sep 2014 13:31:06 +1000	[thread overview]
Message-ID: <1410924666.1586.2.camel@concordia> (raw)
In-Reply-To: <54183371.7020901@linux.vnet.ibm.com>

On Tue, 2014-09-16 at 07:56 -0500, Nathan Fontenot wrote:
> On 08/19/2014 05:55 PM, Anton Blanchard wrote:
> > diff --git a/arch/powerpc/platforms/pseries/dlpar.c b/arch/powerpc/platforms/pseries/dlpar.c
> > index a2450b8..d37ba4f 100644
> > --- a/arch/powerpc/platforms/pseries/dlpar.c
> > +++ b/arch/powerpc/platforms/pseries/dlpar.c
> > @@ -334,7 +334,7 @@ int dlpar_acquire_drc(u32 drc_index)
> >  	return 0;
> >  }
> >  
> > -int dlpar_release_drc(u32 drc_index)
> > +static int dlpar_release_drc(u32 drc_index)
> >  {
> >  	int dr_status, rc;
> 
> Anton, if you're going to do a v2 of these patches you could leave out
> the routines in dlpar.c. I just sent a patch out that exports these two
> functions for memory hotplug updates.

Yep I've dropped those hunks in my tree.

ps. Please trim your replies :)

cheers

      reply	other threads:[~2014-09-17  3:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 22:55 [PATCH 1/4] powerpc: Make a bunch of things static Anton Blanchard
2014-08-19 22:55 ` [PATCH 2/4] powerpc: Ensure global functions include their prototype Anton Blanchard
2014-08-19 22:55 ` [PATCH 3/4] powerpc: Remove stale function prototypes Anton Blanchard
2014-08-19 22:55 ` [PATCH 4/4] powerpc: Move htab_remove_mapping function prototype into header file Anton Blanchard
2014-08-22 15:29   ` Stephen Rothwell
2014-09-11 21:55     ` Anton Blanchard
2014-09-16 12:56 ` [PATCH 1/4] powerpc: Make a bunch of things static Nathan Fontenot
2014-09-17  3:31   ` Michael Ellerman [this message]

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=1410924666.1586.2.camel@concordia \
    --to=mpe@ellerman.id.au \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    /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).