The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Reza Arbab <arbab@linux.vnet.ibm.com>,
	Balbir Singh <bsingharora@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Fwd: [PATCH 1/1] of/fdt: failed to mark hotplug range message
Date: Thu, 22 Dec 2016 13:31:38 -0800	[thread overview]
Message-ID: <585C463A.3080102@gmail.com> (raw)
In-Reply-To: <5251e7ef-cadf-7833-9a7e-66ebf78e2e94@gmx.de>

And the patch to be fixed was merged via akpm, so adding him.

Fixes: 41a9ada3e6b4 ("of/fdt: mark hotpluggable memory")

-Frank

On 12/21/16 21:52, Heinrich Schuchardt wrote:
> scripts/get_maintainers.pl did not show the people involved in creating
> the code to be changed.
> 
> On 12/22/2016 06:34 AM, Heinrich Schuchardt wrote:
>> If marking a hotplug range fails a message
>> "failed to mark hotplug range" is written.
>>
>> The end address is base + size - 1.
>>
>> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
>> ---
>>  drivers/of/fdt.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
>> index c9b5cac03b36..fd129b6e5396 100644
>> --- a/drivers/of/fdt.c
>> +++ b/drivers/of/fdt.c
>> @@ -1057,7 +1057,7 @@ int __init early_init_dt_scan_memory(unsigned long node, const char *uname,
>>  
>>  		if (early_init_dt_mark_hotplug_memory_arch(base, size))
>>  			pr_warn("failed to mark hotplug range 0x%llx - 0x%llx\n",
>> -				base, base + size);
>> +				base, base + size - 1);
>>  	}
>>  
>>  	return 0;
>>
> 
> 

  reply	other threads:[~2016-12-22 21:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22  5:34 [PATCH 1/1] of/fdt: failed to mark hotplug range message Heinrich Schuchardt
2016-12-22  5:52 ` Fwd: " Heinrich Schuchardt
2016-12-22 21:31   ` Frank Rowand [this message]
2016-12-22 21:49   ` Reza Arbab
2016-12-22 22:58     ` Heinrich Schuchardt

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=585C463A.3080102@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arbab@linux.vnet.ibm.com \
    --cc=bsingharora@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=xypron.glpk@gmx.de \
    /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