On 08/09/19 7:01 PM, Bartosz Golaszewski wrote: > sob., 7 wrz 2019 o 10:21 Arnd Bergmann <a...@arndb.de> napisał(a): >> >> On Wed, Aug 28, 2019 at 9:55 AM Bartosz Golaszewski >> <bgolaszew...@baylibre.com> wrote: >>> śr., 28 sie 2019 o 09:44 Sekhar Nori <nsek...@ti.com> napisał(a): >>> >>> Actually I tested this without the clocksource conversion and it works >>> - the previous driver still selects relevant config options. But I >>> think you're right - it's worth picking up all the bug fixes from this >>> series and then merging the rest once dm365 issue is fixed. >> >> I just had another look at the series and found that the driver fixes >> (patches 1 and 2) are queued in linux-next, and patch 3 was merged. >> >> If you like, I could put the remaining two patches into the arm/late branch >> and send that after the media and staging trees are merged into mainline. >> >> Arnd > > Sure! Makes sense. > > Sekhar: this series doesn't break current mainline (i.e. without the > clocksource series) so I think we're safe even for dm365.
Yes, I boot/NFS tested the two patches applied on latest linux-next on on all 6 DaVinci SoCs. I have acked the patches in case Arnd will apply them directly to ARM-SoC. Thanks, Sekhar
