[Greg] > [Me] > > + spin_lock(&amba_bustype.p->klist_drivers.k_lock); > > Ick, nope, you can't do this, sorry. That's a "private" structure for > a reason. Yeah I get it, but in the platform bus case what's that traversal of the klists actually for? I didn't get it, and was guessing that it was considering the case where devices spawn new devices. > So what's the real driving force here, just saving a few hundred bytes > after booting? Or something else? A few thousand actually according to Russells measurements. And no I don't think it's worth it unless someone else challenge this... Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
