[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081206121227.GA6292@wotan.suse.de>
Date: Sat, 6 Dec 2008 13:12:27 +0100
From: Nick Piggin <npiggin@...e.de>
To: Nick Andrew <nick@...k-andrew.net>
Cc: Christoph Lameter <cl@...ux-foundation.org>,
Hugh Dickins <hugh@...itas.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Rik van Riel <riel@...hat.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH] Fix incorrect use of loose in migrate.c
On Fri, Dec 05, 2008 at 02:08:07PM +1100, Nick Andrew wrote:
> Fix incorrect use of loose in migrate.c
>
> It should be 'lose', not 'loose'.
>
> Signed-off-by: Nick Andrew <nick@...k-andrew.net>
> ---
>
> mm/migrate.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
>
> diff --git a/mm/migrate.c b/mm/migrate.c
> index 1e0d6b2..7605b2b 100644
> --- a/mm/migrate.c
> +++ b/mm/migrate.c
> @@ -514,7 +514,7 @@ static int writeout(struct address_space *mapping, struct page *page)
> /*
> * A dirty page may imply that the underlying filesystem has
> * the page on some queue. So the page must be clean for
> - * migration. Writeout may mean we loose the lock and the
> + * migration. Writeout may mean we lose the lock and the
> * page state is no longer what we checked for earlier.
> * At this point we know that the migration attempt cannot
> * be successful.
I don't know... presumably we haven't just gone and lost the little
bugger. I mean, we were holding it one minute, then... gone? Do we
have Alzheimer's? Unlikely. I think we loosed it.
--
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