Re: [PATCH V2] clk: zynq: do not allow kmalloc failure

2018-11-30 Thread Nicholas Mc Guire
On Fri, Nov 30, 2018 at 12:09:30AM -0800, Stephen Boyd wrote: > Quoting Nicholas Mc Guire (2018-11-29 23:54:53) > > On Thu, Nov 29, 2018 at 03:45:23PM -0800, Stephen Boyd wrote: > > > Quoting Nicholas Mc Guire (2018-11-21 04:28:30) > > > > The kmalloc here is small (< 16 bytes) and occurs during in

Re: [PATCH V2] clk: zynq: do not allow kmalloc failure

2018-11-30 Thread Stephen Boyd
Quoting Nicholas Mc Guire (2018-11-29 23:54:53) > On Thu, Nov 29, 2018 at 03:45:23PM -0800, Stephen Boyd wrote: > > Quoting Nicholas Mc Guire (2018-11-21 04:28:30) > > > The kmalloc here is small (< 16 bytes) and occurs during initialization > > > during system startup here (can not be built as mod

Re: [PATCH V2] clk: zynq: do not allow kmalloc failure

2018-11-29 Thread Nicholas Mc Guire
On Thu, Nov 29, 2018 at 03:45:23PM -0800, Stephen Boyd wrote: > Quoting Nicholas Mc Guire (2018-11-21 04:28:30) > > The kmalloc here is small (< 16 bytes) and occurs during initialization > > during system startup here (can not be built as module) thus if this > > kmalloc failed it is an indication

Re: [PATCH V2] clk: zynq: do not allow kmalloc failure

2018-11-29 Thread Stephen Boyd
Quoting Nicholas Mc Guire (2018-11-21 04:28:30) > The kmalloc here is small (< 16 bytes) and occurs during initialization > during system startup here (can not be built as module) thus if this > kmalloc failed it is an indication of something more serious going on > and it is fine to hang the syste

[PATCH V2] clk: zynq: do not allow kmalloc failure

2018-11-21 Thread Nicholas Mc Guire
The kmalloc here is small (< 16 bytes) and occurs during initialization during system startup here (can not be built as module) thus if this kmalloc failed it is an indication of something more serious going on and it is fine to hang the system here rather than cause some harder to understand error