From: Scott Wood <scottwood@freescale.com>
To: Zhao Qiang <B45475@freescale.com>
Cc: <linuxppc-dev@lists.ozlabs.org>, <B07421@freescale.com>,
<R63061@freescale.com>
Subject: Re: [PATCH 1/2] qe_common: add qe common functions into qe_common.c
Date: Wed, 27 May 2015 17:51:14 -0500 [thread overview]
Message-ID: <1432767074.4089.51.camel@freescale.com> (raw)
In-Reply-To: <1432717920-43563-1-git-send-email-B45475@freescale.com>
On Wed, 2015-05-27 at 17:11 +0800, Zhao Qiang wrote:
> +int qe_muram_init(void)
> +{
> + struct device_node *np;
> + struct resource r;
> + u32 zero[OF_MAX_ADDR_CELLS] = {};
> + resource_size_t max = 0;
> + int i = 0;
> + int ret = 0;
> +
> + if (muram_pbase)
> + return 0;
> +
> + spin_lock_init(&qe_muram_lock);
> + /* initialize the info header */
> + rh_init(&qe_muram_info, 1,
> + sizeof(qe_boot_muram_rh_block) /
> + sizeof(qe_boot_muram_rh_block[0]),
> + qe_boot_muram_rh_block);
NACK (see patch 2/2), and even if rheap were acceptable that would
have needed to come before patches using it outside arch/powerpc.
-Scott
prev parent reply other threads:[~2015-05-27 22:51 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
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 ` Scott Wood [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=1432767074.4089.51.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B45475@freescale.com \
--cc=R63061@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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 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.