Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754589Ab3J2LpM (ORCPT ); Tue, 29 Oct 2013 07:45:12 -0400 Received: from mail-oa0-f41.google.com ([209.85.219.41]:40780 "EHLO mail-oa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751237Ab3J2LpL (ORCPT ); Tue, 29 Oct 2013 07:45:11 -0400 MIME-Version: 1.0 In-Reply-To: <1383043819-9123-1-git-send-email-tushar.behera@linaro.org> References: <1383043819-9123-1-git-send-email-tushar.behera@linaro.org> Date: Tue, 29 Oct 2013 17:15:10 +0530 Message-ID: Subject: Re: [PATCH] clk: Zero-initialize memory for new clock in devm_clk_register From: Tushar Behera To: lkml , "linux-arm-kernel@lists.infradead.org" Cc: mturquette , Patch Tracking Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 959 Lines: 24 On 29 October 2013 16:20, Tushar Behera wrote: > Earlier to commit 64c862a839a8 ("devres: add kernel standard devm_k.alloc > functions") devres_alloc API used to zero-initialize the devres > allocated object, but now only the devres header is zero-initialized. > > Since clk_register zero-initializes the memory while allocating for > a new clock, passing explicit flag __GFP_ZERO to devres_alloc in > devm_clk_register to match the behaviour. > > Signed-off-by: Tushar Behera > --- Please ignore this patch. Kevin Hilman already has got a nicer patch [1] that fixes this problem at a generic level. [1] https://lkml.org/lkml/2013/10/19/5 -- Tushar Behera -- 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/