Re: [PATCH 3/3] irqchip/gic: assign irqchip dynamically

2015-12-10 Thread Linus Walleij
On Wed, Dec 9, 2015 at 3:15 PM, Marc Zyngier wrote: > If you're OK with this and the previous patch, I'll squash those into > the original ones, and put it on a branch for Thomas to pick up for 4.5. OK go ahead. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH 3/3] irqchip/gic: assign irqchip dynamically

2015-12-10 Thread Linus Walleij
On Wed, Dec 9, 2015 at 3:15 PM, Marc Zyngier wrote: > If you're OK with this and the previous patch, I'll squash those into > the original ones, and put it on a branch for Thomas to pick up for 4.5. OK go ahead. Yours, Linus Walleij -- To unsubscribe from this list: send

Re: [PATCH 3/3] irqchip/gic: assign irqchip dynamically

2015-12-09 Thread Marc Zyngier
On 23/10/15 23:15, Linus Walleij wrote: > Instead of having the irqchip being a static struct, make it part > of the per-instance data so we can assign it a dynamic name. This > has the usable side effect of displaying the GIC with an instance > number as GIC0, GIC1 ... GICn in /proc/interrupts,

Re: [PATCH 3/3] irqchip/gic: assign irqchip dynamically

2015-12-09 Thread Marc Zyngier
On 23/10/15 23:15, Linus Walleij wrote: > Instead of having the irqchip being a static struct, make it part > of the per-instance data so we can assign it a dynamic name. This > has the usable side effect of displaying the GIC with an instance > number as GIC0, GIC1 ... GICn in /proc/interrupts,

[PATCH 3/3] irqchip/gic: assign irqchip dynamically

2015-10-23 Thread Linus Walleij
Instead of having the irqchip being a static struct, make it part of the per-instance data so we can assign it a dynamic name. This has the usable side effect of displaying the GIC with an instance number as GIC0, GIC1 ... GICn in /proc/interrupts, which is helpful when debugging cascaded GICs,

[PATCH 3/3] irqchip/gic: assign irqchip dynamically

2015-10-23 Thread Linus Walleij
Instead of having the irqchip being a static struct, make it part of the per-instance data so we can assign it a dynamic name. This has the usable side effect of displaying the GIC with an instance number as GIC0, GIC1 ... GICn in /proc/interrupts, which is helpful when debugging cascaded GICs,