On Sat, 2013-10-19 at 19:57 -0700, Greg KH wrote: > On Fri, Oct 18, 2013 at 10:52:46PM -0700, Kevin Hilman wrote: > > Greg KH <gre...@linuxfoundation.org> writes: > > > > > On Fri, Oct 18, 2013 at 10:04:11AM -0700, Kevin Hilman wrote: > > >> > A handful of boot panics on ARM platforms were bisected to point at > > >> > the version of this commit that's in linux-next (commit > > >> > 64c862a839a8db2c02bbaa88b923d13e1208919d). Reverting this commit > > >> > makes things happy again. > > >> > > > >> > Upon further digging, it seems that users of devres_alloc() are > > >> > relying on the previous behavior of having the memory zero'd which is > > >> > no longer the case after $SUBJECT patch. The change below on top of > > >> > -next makes these ARM boards happy again. > > >> > > >> Oops, it should've fixed __devres_alloc() also. Updated patch below. > > > > > > Can you send this in a format that I can apply it in? It was whitespace > > > damaged. > > > > hmm, sorry about that. This one should work, though I wonder if Andrew > > should pick this up since I think the patch that causes the breakage > > came through his tree. > > No, the patch is in my tree, not Andrew's. > > Joe, can I get a signed-off-by for this?
If you want. Signed-off-by: Joe Perches <j...@perches.com> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
