Messages in this thread | | | From | Geert Uytterhoeven <> | Date | Mon, 25 Mar 2019 10:25:36 +0100 | Subject | Re: [PATCH v4 00/14] m68k: Drop arch_gettimeoffset and adopt clocksource API |
| |
Hi Finn,
On Tue, Mar 5, 2019 at 10:55 AM Finn Thain <fthain@telegraphics.com.au> wrote: > On Tue, 5 Mar 2019, Geert Uytterhoeven wrote: > > On Tue, Mar 5, 2019 at 7:13 AM Finn Thain <fthain@telegraphics.com.au> 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 any plans to merge this series, Geert? > > > > Has this been tested on all/most platforms? Or do you think is it safe to > > apply regardless? > > > > The amiga, atari and mac patches have been tested. > > The apollo, q40, sun3 and sun3x patches are safe though untested, AFAIK. I > confirmed that, in qemu at least, the default jiffies clocksource will > work, and the patch is trivial. > > 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 and potentially introducing > new bugs).
Thank you, applied and queued for v5.2.
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
| |