[<prev] [next>] [day] [month] [year] [list]
Message-ID: <4E80AF4F.1030706@xenotime.net>
Date: Mon, 26 Sep 2011 09:58:55 -0700
From: Randy Dunlap <rdunlap@...otime.net>
To: Wizard <wizarddewhite@...il.com>
CC: linux-kernel@...r.kernel.org, kamezawa.hiroyu@...fujitsu.com,
linux-mm@...ck.org
Subject: Re: [PATCH] fix find_next_system_ram comments
On 09/26/2011 06:58 AM, Wizard wrote:
> The purpose of find_next_system_ram() is to find a the lowest
> memory resource which contain or overlap the [res->start, res->end),
> not just contain.
>
> In this patch, I make this comment more exact and fix one typo.
>
> Signed-off-by: Wizard <wizarddewhite@...il.com>
For Signed-off-by: Documentation/SubmittingPatches says:
using your real name (sorry, no pseudonyms or anonymous contributions.)
> ---
> kernel/resource.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/resource.c b/kernel/resource.c
> index 3b3cedc..2751a8c 100644
> --- a/kernel/resource.c
> +++ b/kernel/resource.c
> @@ -279,7 +279,8 @@ EXPORT_SYMBOL(release_resource);
>
> #if !defined(CONFIG_ARCH_HAS_WALK_MEMORY)
> /*
> - * Finds the lowest memory reosurce exists within [res->start.res->end)
> + * Finds the lowest memory resource which contains or overlaps
> + * [res->start.res->end)
Your patch description uses ", " (comma) here. I think that's better than
keeping the ".".
> * the caller must specify res->start, res->end, res->flags and "name".
> * If found, returns 0, res is overwritten, if not found, returns -1.
> */
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/
Powered by blists - more mailing lists