On Sun, Nov 1, 2020 at 4:47 AM Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx> wrote:
>
> On Fri, 30 Oct 2020, Arnd Bergmann wrote:
>
> > CONFIG_ARCH_GETTIMEOFFSET has been gradually phased out from all
> > platforms, with only ARM EBSA110 recently. As this has no more known
> > users, the first three patches remove EBSA110 along with one platform
> > specific driver and the ARCH_GETTIMEOFFSET infrastructure.
> >
>
> The CONFIG_ARCH_GETTIMEOFFSET patches weren't part of v1. Is there some
> kind of dependency here?
There is technically a dependency, though nobody would notice
in practice: removing the ARM timer tick function in patch 6 would
break the ebsa110 platform if we didn't first remove it in patch 1.
Changing ebsa110 to use legacy_timer_tick in turn would introduce
a conflict against the removal patch.
Neither of those is particularly harmful as there are no users of
the affected ebsa110 code, but keeping the two series together
avoids getting complaints from the build bots.
Arnd
