linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Zhao Qiang-B45475 <qiang.zhao@freescale.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
	Xie Xiaobo-R63061 <X.Xie@freescale.com>,
	"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
	Li Yang-Leo-R58472 <LeoLi@freescale.com>,
	"paulus@samba.org" <paulus@samba.org>
Subject: Re: [PATCH V7 2/3] qe_common: add qe_muram_ functions to manage muram
Date: Thu, 10 Sep 2015 17:09:05 -0500	[thread overview]
Message-ID: <1441922945.2909.12.camel@freescale.com> (raw)
In-Reply-To: <SN1PR0301MB1550D133A4FE7FE3DB8870D19B510@SN1PR0301MB1550.namprd03.prod.outlook.com>

On Wed, 2015-09-09 at 21:34 -0500, Zhao Qiang-B45475 wrote:
> On Mon, 2015-09-10 at 12:39 -0500, Wood Scott-B07421 wrote:
> 
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Thursday, September 10, 2015 12:39 AM
> > To: Zhao Qiang-B45475
> > Cc: linux-kernel@vger.kernel.org; linuxppc-dev@lists.ozlabs.org;
> > lauraa@codeaurora.org; Xie Xiaobo-R63061; benh@kernel.crashing.org; Li
> > Yang-Leo-R58472; paulus@samba.org
> > Subject: Re: [PATCH V7 2/3] qe_common: add qe_muram_ functions to manage
> > muram
> > 
> > On Sun, 2015-09-06 at 01:37 -0500, Zhao Qiang-B45475 wrote:
> > > On Mon, 2015-09-2 at 8:34 +0800, Wood Scott-B07421 wrote:
> > > > -----Original Message-----
> > > > From: Wood Scott-B07421
> > > > Sent: Wednesday, September 02, 2015 8:34 AM
> > > > To: Zhao Qiang-B45475
> > > > Cc: linux-kernel@vger.kernel.org; linuxppc-dev@lists.ozlabs.org;
> > > > lauraa@codeaurora.org; Xie Xiaobo-R63061; benh@kernel.crashing.org;
> > > > Li Yang-Leo-R58472; paulus@samba.org
> > > > Subject: Re: [PATCH V7 2/3] qe_common: add qe_muram_ functions to
> > > > manage muram
> > > > 
> > > > On Mon, 2015-08-31 at 16:58 +0800, Zhao Qiang wrote:
> > > > 
> > > > > @@ -187,12 +190,25 @@ static inline int
> > > > > qe_alive_during_sleep(void)  }
> > > > > 
> > > > >  /* we actually use cpm_muram implementation, define this for
> > > > > convenience */ -#define qe_muram_init cpm_muram_init -#define
> > > > > qe_muram_alloc cpm_muram_alloc -#define qe_muram_alloc_fixed
> > > > > cpm_muram_alloc_fixed -#define qe_muram_free cpm_muram_free
> > > > > -#define qe_muram_addr cpm_muram_addr -#define qe_muram_offset
> > > > > cpm_muram_offset
> > > > > +#define cpm_muram_init qe_muram_init #define cpm_muram_alloc
> > > > > +qe_muram_alloc #define cpm_muram_alloc_fixed qe_muram_alloc_fixed
> > > > > +#define cpm_muram_free qe_muram_free #define cpm_muram_addr
> > > > > +qe_muram_addr #define cpm_muram_offset qe_muram_offset
> > > > 
> > > > Why?  This is unnecessary churn.
> > > > 
> > > This is necessary. QE is on both ARM and PowerPC, its code is under
> > > public code.
> > > But CPM is only on PowerPC and its code is under PowerPC.
> > > So when build ARM, QE will not find cpm_muram_* function.
> > 
> > If you move the cpm_muram functions to drivers/soc, then ARM will find
> > them.
> > There is no need to rename them.
> 
> Yes, moving cpm_muram can handle this issue. However, cpm is not necessary
> To move to public code, and a churn is simpler than moving cpm_muram.
> Please consider my suggestion, Thank you!

What do you mean by "public code"?  You're already moving cpm_muram.  I'm 
just asking that you not rename it while you do so.  If it absolutely must be 
renamed, do it in a different patch from the one that moves the code, though I
don't see why the rename is helpful.

-Scott

  reply	other threads:[~2015-09-10 22:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  8:58 [PATCH V7 1/3] genalloc:support memory-allocation with bytes-alignment to genalloc Zhao Qiang
2015-08-31  8:58 ` [PATCH V7 2/3] qe_common: add qe_muram_ functions to manage muram Zhao Qiang
2015-09-02  0:34   ` Scott Wood
2015-09-02  2:22     ` Zhao Qiang
2015-09-02  2:30       ` Scott Wood
2015-09-02  2:32         ` Zhao Qiang
2015-09-06  6:37     ` Zhao Qiang
2015-09-09 16:38       ` Scott Wood
2015-09-10  2:34         ` Zhao Qiang
2015-09-10 22:09           ` Scott Wood [this message]
2015-09-11  1:59             ` Zhao Qiang
2015-09-11  2:05               ` Scott Wood
2015-08-31  8:58 ` [PATCH V7 3/3] QE: Move QE from arch/powerpc to drivers/soc Zhao Qiang
2015-09-02  0:30 ` [PATCH V7 1/3] genalloc:support memory-allocation with bytes-alignment to genalloc Scott Wood
2015-09-02  2:10   ` Zhao Qiang
2015-09-02  2:18     ` Scott Wood
2015-09-02  2:29       ` Zhao Qiang
2015-09-02  2:33         ` Scott Wood
2015-09-02  3:05           ` Zhao Qiang
2015-09-02  3:08             ` Scott Wood
2015-09-02  3:57               ` Zhao Qiang
2015-09-02  4:51                 ` Scott Wood
2015-09-06  3:13       ` Zhao Qiang
2015-09-09 16:37         ` Scott Wood
2015-09-10  2:26           ` Zhao Qiang
2015-09-10 22:07             ` Scott Wood
2015-09-11  2:09               ` Zhao Qiang
2015-09-11  2:15                 ` Scott Wood
2015-09-11  2:25                   ` Zhao Qiang

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=1441922945.2909.12.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=LeoLi@freescale.com \
    --cc=X.Xie@freescale.com \
    --cc=benh@kernel.crashing.org \
    --cc=lauraa@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=qiang.zhao@freescale.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).