linux-kernel - Re: [PATCH] mm:cma - Fix for typos in comments.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <xa1tr3q4ps94.fsf@mina86.com>
Date:	Mon, 25 May 2015 17:54:31 +0200
From:	Michal Nazarewicz <mina86@...a86.com>
To:	Shailendra Verma <shailendra.capricorn@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Joonsoo Kim <iamjoonsoo.kim@....com>,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
	Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>,
	Sasha Levin <sasha.levin@...cle.com>, linux-mm@...ck.org
Cc:	linux-kernel@...r.kernel.org,
	Shailendra Verma <shailendra.capricorn@...il.com>
Subject: Re: [PATCH] mm:cma - Fix for typos in comments.

On Sat, May 23 2015, Shailendra Verma wrote:
> Signed-off-by: Shailendra Verma <shailendra.capricorn@...il.com>
Acked-by: Michal Nazarewicz <mina86@...a86.com>

> ---
>  mm/cma.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/cma.c b/mm/cma.c
> index 3a7a67b..6612780 100644
> --- a/mm/cma.c
> +++ b/mm/cma.c
> @@ -182,7 +182,7 @@ int __init cma_init_reserved_mem(phys_addr_t base, phys_addr_t size,
>  	if (!size || !memblock_is_region_reserved(base, size))
>  		return -EINVAL;
>  
> -	/* ensure minimal alignment requied by mm core */
> +	/* ensure minimal alignment required by mm core */
>  	alignment = PAGE_SIZE << max(MAX_ORDER - 1, pageblock_order);
>  
>  	/* alignment should be aligned with order_per_bit */
> @@ -238,7 +238,7 @@ int __init cma_declare_contiguous(phys_addr_t base,
>  	/*
>  	 * high_memory isn't direct mapped memory so retrieving its physical
>  	 * address isn't appropriate.  But it would be useful to check the
> -	 * physical address of the highmem boundary so it's justfiable to get
> +	 * physical address of the highmem boundary so it's justifiable to get
>  	 * the physical address from it.  On x86 there is a validation check for
>  	 * this case, so the following workaround is needed to avoid it.
>  	 */
> -- 
> 1.7.9.5
>

-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  Michał “mina86” Nazarewicz    (o o)
ooo +--<mpn@...gle.com>--<xmpp:mina86@...ber.org>--ooO--(_)--Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/