Hi Finn, On Sun, Jul 22, 2018 at 1:56 PM Finn Thain <fth...@telegraphics.com.au> wrote: > On Wed, 18 Jul 2018, I wrote: > > On Wed, 18 Jul 2018, Arnd Bergmann wrote: > > > I'd suggest we do it like below to make it consistent with the rest > > > again, using the 1904..2040 range of dates and no warning for invalid > > > dates. > > > > > > If you agree, I'll send that as a proper patch. > > > > Geert may instead wish to fixup or revert the patch he has committed > > already... > > Geert, how do you want to handle this? > > Do you want a fixup patch or a v3 patch with the WARN_ON and the other two > issues addressed?
Please send a fixup patch, for the m68k/master branch, which is non-rebasing. I'll fold it into the original commit on the m68k/for-next branch. > I'm willing to send either one if Arnd is okay with that. I'd really like > to resolve this before the merge window opens, since my PMU patch series > is affected. +1. If it's not resolved (a few days) before the merge window opens, I may have to revert the patch instead. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@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 -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html