Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753217AbaKKKbi (ORCPT ); Tue, 11 Nov 2014 05:31:38 -0500 Received: from mail-ig0-f173.google.com ([209.85.213.173]:45683 "EHLO mail-ig0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752104AbaKKKbg convert rfc822-to-8bit (ORCPT ); Tue, 11 Nov 2014 05:31:36 -0500 MIME-Version: 1.0 In-Reply-To: References: <1414825380-15322-1-git-send-email-acourbot@nvidia.com> Date: Tue, 11 Nov 2014 11:31:35 +0100 Message-ID: Subject: Re: [RFC] gpio: remove gpio_descs global array From: Linus Walleij To: Alexandre Courbot Cc: Alexandre Courbot , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 4, 2014 at 10:10 AM, Alexandre Courbot wrote: > 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... :) лес рубят — щепки летят as the russians say. Let us have the patch. Yours, Linus Walleij -- 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/