[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20121107115610.c0cb650c.akpm@linux-foundation.org>
Date: Wed, 7 Nov 2012 11:56:10 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Rafael Aquini <aquini@...hat.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
Rusty Russell <rusty@...tcorp.com.au>,
"Michael S. Tsirkin" <mst@...hat.com>,
Rik van Riel <riel@...hat.com>, Mel Gorman <mel@....ul.ie>,
Andi Kleen <andi@...stfloor.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Minchan Kim <minchan@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH v11 1/7] mm: adjust
address_space_operations.migratepage() return code
On Wed, 7 Nov 2012 01:05:48 -0200
Rafael Aquini <aquini@...hat.com> wrote:
> This patch introduces MIGRATEPAGE_SUCCESS as the default return code
> for address_space_operations.migratepage() method and documents the
> expected return code for the same method in failure cases.
I hit a large number of rejects applying this against linux-next. Due
to the increasingly irritating sched/numa code in there.
I attempted to fix it up and also converted some (but not all) of the
implicit tests of `rc' against zero.
Please check the result very carefully - more changes will be needed.
All those
- if (rc)
+ if (rc != MIGRATEPAGE_SUCCESS)
changes are a pain. Perhaps we shouldn't bother.
--
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