Fix incorrect use of loose in migrate.c
It should be 'lose', not 'loose'.
Signed-off-by: Nick Andrew <[email protected]>
---
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.
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 <[email protected]>
> ---
>
> 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.
On Sat, Dec 06, 2008 at 01:12:27PM +0100, Nick Piggin wrote:
> > /*
> > * 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.
Loosen?
Nick.
On Sun, 07 Dec 2008 00:55:36 +1100, Nick Andrew said:
> On Sat, Dec 06, 2008 at 01:12:27PM +0100, Nick Piggin wrote:
> > 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.
>
> Loosen?
"Cry Cheeble, and loose the hamsters of war!"