Hi Kalle Valo, On 01/07/16 11:02, Kalle Valo wrote: > Uri Mashiach <uri.mashiach@xxxxxxxxxxxxxx> writes: > >> Device tree modifications: >> - Pinmux for SPI0 and WiFi GPIOs. >> - SPI0 node with wlcore as a child node. >> >> Cc: Tony Lindgren <tony@xxxxxxxxxxx> >> Signed-off-by: Uri Mashiach <uri.mashiach@xxxxxxxxxxxxxx> >> --- Uri, please document the dependencies next time. Thanks! >> v1 -> v2: Replace interrupts and interrupt-parent with interrupts-extended. >> v2 -> v3: Move the pinctrl-0 = <&wifi_pins> to the wlcore node. >> v3 -> v4: replace interrupts-extended with interrupts and interrupt-parent. (revert v2 modification). >> According to Rob Herring and Documentation/devicetree/bindings/interrupt-controller/interrupts.txt, >> interrupts-extended should only be used when a device has multiple interrupt parents. >> >> arch/arm/boot/dts/am335x-cm-t335.dts | 55 ++++++++++++++++++++++++++++++++++++ >> 1 file changed, 55 insertions(+) > > To what tree should this patch go? My wireless-drivers-next tree doesn't > even have this file. Right. It will hit the mainline during this merge window through Tony's and arm-soc trees. Do you think it will be sensible if you take 1/3 and 2/3 patches and Tony will take the 3/3 (there is no code dependency between first two and the last one), or we can just wait till arm-soc hits the mainline, so you will have the needed code? > > https://patchwork.kernel.org/patch/7933441/ > -- Regards, Igor. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
