Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752567AbaKDJKl (ORCPT ); Tue, 4 Nov 2014 04:10:41 -0500 Received: from mail-ig0-f173.google.com ([209.85.213.173]:41792 "EHLO mail-ig0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752380AbaKDJKh (ORCPT ); Tue, 4 Nov 2014 04:10:37 -0500 MIME-Version: 1.0 In-Reply-To: References: <1414825380-15322-1-git-send-email-acourbot@nvidia.com> From: Alexandre Courbot Date: Tue, 4 Nov 2014 18:10:16 +0900 Message-ID: Subject: Re: [RFC] gpio: remove gpio_descs global array To: Linus Walleij Cc: Alexandre Courbot , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 3, 2014 at 11:11 PM, Linus Walleij wrote: > On Sat, Nov 1, 2014 at 8:03 AM, Alexandre Courbot wrote: > >> The issue with this patch is its use of kzalloc() in gpiochip_add(), a >> function potentially called during early boot, before kzalloc() becomes >> usable. Hence its [RFC] status until we can find a solution for this or >> agree that this issue is actually never ran into (from which point can >> one use kzalloc()?) > > So which driver requires that the gpiochip be statically defined... > I heard about early call but not *that* early. Let me know if you feel adventurous - in that case I will submit a proper version of this patch to put in -next, and we'll see if people complain... :) -- 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/