From: Scott Wood <scottwood@freescale.com>
To: Zhao Qiang-B45475 <qiang.zhao@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"Xie Xiaobo-R63061" <X.Xie@freescale.com>
Subject: Re: [PATCH 2/2] rheap: move rheap.c from arch/powerpc/lib/ to lib/
Date: Tue, 7 Jul 2015 22:27:57 -0500 [thread overview]
Message-ID: <1436326077.2658.65.camel@freescale.com> (raw)
In-Reply-To: <SN1PR0301MB1550F2C30F1393CA26F4FF3B9B910@SN1PR0301MB1550.namprd03.prod.outlook.com>
On Tue, 2015-07-07 at 22:26 -0500, Zhao Qiang-B45475 wrote:
> Now the point is, genalloc is not so proper to qe muram while rheap is
> written to manage muram,
rheap is not specific to muram.
> if use genalloc instead of rheap, there will be amounts of work to do.
Not much. I think I've spent more time responding to continual e-mails on
this topic than it would have taken to convert it. :-P
> I have a suggestion, how about to put rheap under drivers/soc/qe, because
> rheap is
> To manage muram when it is added to sdk.
No.
-Scott
next prev parent reply other threads:[~2015-07-08 3:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 9:11 [PATCH 1/2] qe_common: add qe common functions into qe_common.c Zhao Qiang
2015-05-27 9:12 ` [PATCH 2/2] rheap: move rheap.c from arch/powerpc/lib/ to lib/ Zhao Qiang
2015-05-27 17:36 ` Scott Wood
2015-06-04 5:56 ` Zhao Qiang
2015-06-04 6:13 ` Scott Wood
2015-06-04 9:27 ` Zhao Qiang
2015-06-04 22:40 ` Scott Wood
2015-07-08 2:54 ` Zhao Qiang
2015-07-08 2:55 ` Scott Wood
2015-07-08 3:26 ` Zhao Qiang
2015-07-08 3:27 ` Scott Wood [this message]
2015-07-08 7:25 ` Zhao Qiang
2015-07-08 18:58 ` Scott Wood
2015-07-09 3:18 ` Zhao Qiang
2015-07-09 3:50 ` Scott Wood
2015-07-09 6:05 ` Zhao Qiang
2015-07-09 6:09 ` Scott Wood
2015-07-09 6:14 ` Zhao Qiang
2015-07-09 6:47 ` Scott Wood
2015-05-27 22:51 ` [PATCH 1/2] qe_common: add qe common functions into qe_common.c Scott Wood
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=1436326077.2658.65.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=X.Xie@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.