From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>, linuxppc-dev@ozlabs.org
Cc: mikey@neuling.org
Subject: Re: [PATCH] powerpc/prom: Use DRCONF flags while processing detected LMBs
Date: Fri, 07 Aug 2015 07:49:48 +0530 [thread overview]
Message-ID: <55C415C4.9080704@linux.vnet.ibm.com> (raw)
In-Reply-To: <1438866307-19637-1-git-send-email-khandual@linux.vnet.ibm.com>
On Thursday 06 August 2015 06:35 PM, Anshuman Khandual wrote:
> This patch just replaces hard coded values with existing
Please drop "This patch just" and start with "Replace hard ..."
https://www.kernel.org/doc/Documentation/SubmittingPatches
Maddy
> DRCONF flags while procesing detected LMBs from the device
> tree. This does not change any functionality.
>
> Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
> ---
> arch/powerpc/kernel/prom.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/arch/powerpc/kernel/prom.c b/arch/powerpc/kernel/prom.c
> index 8b888b1..70a8cab 100644
> --- a/arch/powerpc/kernel/prom.c
> +++ b/arch/powerpc/kernel/prom.c
> @@ -476,9 +476,10 @@ static int __init early_init_dt_scan_drconf_memory(unsigned long node)
> flags = of_read_number(&dm[3], 1);
> /* skip DRC index, pad, assoc. list index, flags */
> dm += 4;
> - /* skip this block if the reserved bit is set in flags (0x80)
> - or if the block is not assigned to this partition (0x8) */
> - if ((flags & 0x80) || !(flags & 0x8))
> + /* skip this block if the reserved bit is set in flags
> + or if the block is not assigned to this partition */
> + if ((flags & DRCONF_MEM_RESERVED) ||
> + !(flags & DRCONF_MEM_ASSIGNED))
> continue;
> size = memblock_size;
> rngs = 1;
next prev parent reply other threads:[~2015-08-07 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 13:05 [PATCH] powerpc/prom: Use DRCONF flags while processing detected LMBs Anshuman Khandual
2015-08-07 2:19 ` Madhavan Srinivasan [this message]
2015-08-10 21:48 ` Michael Ellerman
2015-08-12 6:23 ` Anshuman Khandual
2015-08-13 1:44 ` Michael Ellerman
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=55C415C4.9080704@linux.vnet.ibm.com \
--to=maddy@linux.vnet.ibm.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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).