[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161222214917.7g6ldgkdvrlqsyq3@arbab-laptop.austin.ibm.com>
Date: Thu, 22 Dec 2016 15:49:18 -0600
From: Reza Arbab <arbab@...ux.vnet.ibm.com>
To: Heinrich Schuchardt <xypron.glpk@....de>
Cc: Balbir Singh <bsingharora@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Fwd: [PATCH 1/1] of/fdt: failed to mark hotplug range message
On Thu, Dec 22, 2016 at 06:52:45AM +0100, Heinrich Schuchardt wrote:
> 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;
Isn't it implied that ranges printed this way are [start, end)?
If not, the entire file should be fixed, not just this occurrence.
--
Reza Arbab
Powered by blists - more mailing lists