Hi Linus, On 02/12/2014 05:03 PM, Linus Walleij wrote:
On Wed, Feb 5, 2014 at 4:47 PM, Grygorii Strashko <[email protected]> wrote:The similar GPIO HW block is used by keystone SoCs as in Davinci SoCs. Hence, reuse Davinci GPIO driver for Keystone taking into account that Keystone contains ARM GIC IRQ controller which is implemented using IRQ Chip. Documentation: http://www.ti.com/lit/ug/sprugv1/sprugv1.pdf Acked-by: Santosh Shilimkar <[email protected]> Acked-by: Linus Walleij <[email protected]> Signed-off-by: Grygorii Strashko <[email protected]> --- Changes in v4: - rebased on top of v3.14 + [patch] gpio: davinci: signedness bug in davinci_gpio_irq_setup()I tried applying this and it does not apply on the "devel" branch in the GPIO tree. Since I haven't touched one line of code in the DaVinci driver since v3.14-rc1 I seriously doubt that this is rebased on v3.14[-rc]. Can you please rebase the patch onto v3.14-rc1 for real and resend it?
Sorry, But I've to clarify that this patch is based on: http://www.spinics.net/lists/linux-kernel-janitors/msg18017.html [patch] gpio: davinci: signedness bug in davinci_gpio_irq_setup() And I did it to avoid merge conflicts between these two patches. Is it possible to apply above one first? It's not in any of your branches. Of Course, I can re-base this patch on clean v3.14-rc1, but then merge conflict will happen with "gpio: davinci: signedness.." patch. Regards, - grygorii -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
