Hi Greg, Finn,
On Fri, Apr 27, 2018 at 3:33 AM, Greg Ungerer <gerg@xxxxxxxxxxxxxx> wrote:
On 27/04/18 11:12, Finn Thain wrote:
My earlier fix for read_persistent_clock() neglected to cover
m68328_hwclk(). Correct this oversight.
Cc: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
Signed-off-by: Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx>
---
Greg, the read_persistent_clock() change has already been queued
by Geert. Should this patch be pushed together with that one
(presuming your ack)? Sorry for the inconvenience.
If Geert is happy to add it to his tree that would seem to make sense.
Otherwise I can take it via the m68knommu tree. Either way:
Acked-by: Greg Ungerer <gerg@xxxxxxxxxxxxxx>
I'm reconsidering.
I'll apply it to my tree, and fold it into the original fix for v4.18.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
