Re: [PATCH] of: Print rather than WARN'ing when overlap check fails

2015-11-10 Thread Michael Ellerman
On Tue, 2015-11-10 at 09:41 +, David Laight wrote: > From: Michael Ellerman > > Sent: 10 November 2015 05:09 > > __rmem_check_for_overlap() is called very early in boot, and on some > > powerpc systems it's not safe to call WARN that early in boot. > > > > If the overlap check fails the

Re: [PATCH] of: Print rather than WARN'ing when overlap check fails

2015-11-10 Thread Michael Ellerman
On Tue, 2015-11-10 at 16:08 +1100, Michael Ellerman wrote: > __rmem_check_for_overlap() is called very early in boot, and on some > powerpc systems it's not safe to call WARN that early in boot. > > If the overlap check fails the system will oops instead of printing a > warning. Furthermore

RE: [PATCH] of: Print rather than WARN'ing when overlap check fails

2015-11-10 Thread David Laight
From: Michael Ellerman > Sent: 10 November 2015 05:09 > __rmem_check_for_overlap() is called very early in boot, and on some > powerpc systems it's not safe to call WARN that early in boot. > > If the overlap check fails the system will oops instead of printing a > warning. Furthermore because