Re: [PATCH 1/9] mm: remove return value from init_currently_empty_zone

2017-04-13 Thread YASUAKI ISHIMATSU
On 04/10/2017 07:03 AM, Michal Hocko wrote: > From: Michal Hocko > > init_currently_empty_zone doesn't have any error to return yet it is > still an int and callers try to be defensive and try to handle potential > error. Remove this nonsense and simplify all callers. > > This patch shouldn't

Re: [PATCH 1/9] mm: remove return value from init_currently_empty_zone

2017-04-13 Thread Vlastimil Babka
On 04/10/2017 01:03 PM, Michal Hocko wrote: > From: Michal Hocko > > init_currently_empty_zone doesn't have any error to return yet it is > still an int and callers try to be defensive and try to handle potential > error. Remove this nonsense and simplify all callers. > > This patch shouldn't ha

Re: [PATCH 1/9] mm: remove return value from init_currently_empty_zone

2017-04-11 Thread Balbir Singh
On Mon, 2017-04-10 at 13:03 +0200, Michal Hocko wrote: > From: Michal Hocko > > init_currently_empty_zone doesn't have any error to return yet it is > still an int and callers try to be defensive and try to handle potential > error. Remove this nonsense and simplify all callers. > > This patch s

[PATCH 1/9] mm: remove return value from init_currently_empty_zone

2017-04-10 Thread Michal Hocko
From: Michal Hocko init_currently_empty_zone doesn't have any error to return yet it is still an int and callers try to be defensive and try to handle potential error. Remove this nonsense and simplify all callers. This patch shouldn't have any visible effect Signed-off-by: Michal Hocko --- i