Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753908Ab3JYM77 (ORCPT ); Fri, 25 Oct 2013 08:59:59 -0400 Received: from mail-qe0-f50.google.com ([209.85.128.50]:37775 "EHLO mail-qe0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751284Ab3JYM75 (ORCPT ); Fri, 25 Oct 2013 08:59:57 -0400 MIME-Version: 1.0 X-Originating-IP: [77.221.165.98] In-Reply-To: <1382282566.2041.39.camel@joe-AO722> References: <1381296747.2040.17.camel@joe-AO722> <20131011131138.3bc5b2acf60df3a5d79d0d24@linux-foundation.org> <20131018225702.GA13090@kroah.com> <8761stu7rl.fsf@linaro.org> <20131020025713.GA22344@kroah.com> <1382282566.2041.39.camel@joe-AO722> Date: Fri, 25 Oct 2013 05:59:56 -0700 Message-ID: Subject: Re: [RFC PATCH] device: Add kernel standard devm_k.alloc functions From: Olof Johansson To: Joe Perches Cc: Greg KH , Kevin Hilman , Andrew Morton , Tejun Heo , LKML , Sangjung Woo , Thierry Reding , Guenter Roeck , linux-arm-kernel Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1827 Lines: 46 On Sun, Oct 20, 2013 at 8:22 AM, Joe Perches wrote: > 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 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 Acked-by: Olof Johansson Greg, would you mind picking this up? It's still broken in -next and I don't want it to mask other issues that might be introduced. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/