On Tue, Nov 4, 2014 at 10:10 AM, Alexandre Courbot <[email protected]> wrote: > On Mon, Nov 3, 2014 at 11:11 PM, Linus Walleij <[email protected]> > wrote: >> On Sat, Nov 1, 2014 at 8:03 AM, Alexandre Courbot <[email protected]> >> 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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
