On 01/14/2016 08:05 AM, Kalle Valo wrote:
Tony Lindgren <tony@xxxxxxxxxxx> writes:
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?
Yeah I'll pick the dts changes separately after the merge window as
there is no dependency to the driver changes.
Ok, I'll then take patches 1 and 2 once the merge window opens.
I guess it is semantics, but the merge window is open right now so you
probably mean to say after the merge window closes, ie. when 4.5-rc1 is
ready.
Regards,
Arend
--
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
