Re: [PATCH v4 00/14] m68k: Drop arch_gettimeoffset and adopt clocksource API

2019-03-25 Thread Geert Uytterhoeven
Hi Finn, On Tue, Mar 5, 2019 at 10:55 AM Finn Thain wrote: > On Tue, 5 Mar 2019, Geert Uytterhoeven wrote: > > On Tue, Mar 5, 2019 at 7:13 AM Finn Thain > > wrote: > > > On Sat, 1 Dec 2018, Finn Thain wrote: > > > > This series removes "select ARCH_USES_GETTIMEOFFSET" from arch/m68k > > > > and

Re: [PATCH v4 00/14] m68k: Drop arch_gettimeoffset and adopt clocksource API

2019-03-05 Thread Linus Walleij
On Tue, Mar 5, 2019 at 10:55 AM Finn Thain wrote: > That leaves bvme6000, hp300, mvme147 and mvme16x. Those have not been > tested. Here are some options for those platforms: > > 1) Apply the patches untested (gaining new clocksources and some API > modernization for m68k, while fixing old bugs a

Re: [PATCH v4 00/14] m68k: Drop arch_gettimeoffset and adopt clocksource API

2019-03-05 Thread Finn Thain
On Tue, 5 Mar 2019, Geert Uytterhoeven wrote: > On Tue, Mar 5, 2019 at 7:13 AM Finn Thain wrote: > > On Sat, 1 Dec 2018, Finn Thain wrote: > > > This series removes "select ARCH_USES_GETTIMEOFFSET" from arch/m68k > > > and converts users of arch_gettimeoffset to the clocksource API. > > > Various

Re: [PATCH v4 00/14] m68k: Drop arch_gettimeoffset and adopt clocksource API

2019-03-04 Thread Geert Uytterhoeven
Hi Finn, On Tue, Mar 5, 2019 at 7:13 AM Finn Thain wrote: > On Sat, 1 Dec 2018, Finn Thain wrote: > > This series removes "select ARCH_USES_GETTIMEOFFSET" from arch/m68k > > and converts users of arch_gettimeoffset to the clocksource API. > > Various bugs are fixed along the way. > > Are there an

Re: [PATCH v4 00/14] m68k: Drop arch_gettimeoffset and adopt clocksource API

2019-03-04 Thread Finn Thain
On Sat, 1 Dec 2018, Finn Thain wrote: > This series removes "select ARCH_USES_GETTIMEOFFSET" from arch/m68k > and converts users of arch_gettimeoffset to the clocksource API. > Various bugs are fixed along the way. Are there any plans to merge this series, Geert? --