linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Laura Abbott <labbott@redhat.com>
Cc: Russell King <rmk+kernel@armlinux.org.uk>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	linux-arm-kernel@lists.infradead.org, lilja.magnus@gmail.com,
	festevam@gmail.com, linux-kernel@vger.kernel.org,
	Laura Abbott <lauraa@codeaurora.org>
Subject: Re: [PATCHv2 1/2] arm: Cleanup sanity_check_meminfo
Date: Thu, 5 Jan 2017 23:17:25 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1701052308020.21662@knanqh.ubzr> (raw)
In-Reply-To: <1483657274-11346-2-git-send-email-labbott@redhat.com>

On Thu, 5 Jan 2017, Laura Abbott wrote:

> 
> The logic for sanity_check_meminfo has become difficult to
> follow. Clean up the code so it's more obvious what the code
> is actually trying to do. Additionally, meminfo is now removed
> so rename the function to better describe it's purpose.

s/it's/its/

> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
> Signed-off-by: Laura Abbott <labbott@redhat.com>
> ---
> v2: Fixed code so b9a019899f61 ("ARM: 8590/1: sanity_check_meminfo():
> avoid overflow on vmalloc_limit") should stay fixed. The casting and assignment
> still seem ugly.

Are you referring to the initial vmalloc_limit assignment?

> @@ -1172,43 +1170,19 @@ void __init sanity_check_meminfo(void)
>  	for_each_memblock(memory, reg) {
>  		phys_addr_t block_start = reg->base;
>  		phys_addr_t block_end = reg->base + reg->size;
> -		phys_addr_t size_limit = reg->size;
>  
> -		if (reg->base >= vmalloc_limit)
> -			highmem = 1;
> -		else
> -			size_limit = vmalloc_limit - reg->base;
>  
> -
[...]

This leaves a spurious empty line. One was already there before your 
patch but this would be a good opportunity to remove it.

Other than that...

Reviewed-by: Nicolas Pitre <nico@linaro.org>


Nicolas

  reply	other threads:[~2017-01-06  4:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 23:01 [PATCHv2 0/2] Memblock cleanup plus memory removal fix Laura Abbott
2017-01-05 23:01 ` [PATCHv2 1/2] arm: Cleanup sanity_check_meminfo Laura Abbott
2017-01-06  4:17   ` Nicolas Pitre [this message]
2017-01-10  1:07     ` Laura Abbott
2017-01-05 23:01 ` [PATCHv2 2/2] arm: Adjust memory boundaries after reservations Laura Abbott
2017-01-06  0:41   ` Russell King - ARM Linux
2017-01-06  9:46 ` [PATCHv2 0/2] Memblock cleanup plus memory removal fix Magnus Lilja

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=alpine.LFD.2.20.1701052308020.21662@knanqh.ubzr \
    --to=nicolas.pitre@linaro.org \
    --cc=festevam@gmail.com \
    --cc=grygorii.strashko@ti.com \
    --cc=labbott@redhat.com \
    --cc=lauraa@codeaurora.org \
    --cc=lilja.magnus@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    /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).