Hi Geert,
Am 24.05.2018 um 22:02 schrieb Geert Uytterhoeven:
I happen to have a few old kernel trees around that I can consult for
a rough history, and 2.4.30 still has the comment while 2.6.18 or
2.6.19 lost it.
Of course all historical git trees contain linear history, not the branch
with the continued 2.4.x development after 2.5.x was spun off...
So I guess this was fixed in 2.4.x, but never in 2.5.x :-(
Propagating fixes to the other versions was nowhere near as automatic in
those days.
Linux/m68k CVS had a fix in m68k-2_4_21 and later:
commit 7bfc690086f568f440f81c2bb3578dd07295b303
Author: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
Date: Mon Jul 21 21:36:10 2003 +0000
Take the gap into account in free_io_area() (from Michael Müller)
...
Yep, that's it.
I can't seem to find a public git tree with full 2.4.x history, but
https://git.linux-mips.org/cgit/ralf/linux.git/commit/arch/m68k/mm/kmap.c?h=linux-2.4&id=65456e0e26a40f4c4933d700847ed1a9d261811e
shows it made upstream in 2.4.23-rc1.
Thanks - that shows the bug was introduced in 2.2.1 and went unnoticed
until 2.4.21.
Where is the old CVS hosted these days?
Nowhere.
Ralf Bächle was so kind to provide me with a git import a long time ago
(his machine was more powerful than mine ;-).
I could push it to kernel.org (a separate repo, else linux-m68k.git will grow a
lot, and everyone will suffer ;-). I also have to re-add the various branches
(it has tags only). Anyone interested?
Might be good to have, but probably not worth the effort adding the
missing branches. I'll just bookmark Ralf's tree for now.
Anyway, applied and queued for 4.18, with a cc to stable.
Thanks!
Thanks, I trust Ben will pick this up for Debian once it hits stable ...
Cheers,
Michael
Gr{oetje,eeting}s,
Geert
--
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
