On Sat, Apr 23, 2011 at 03:39:15PM +0000, Thorsten Glaser wrote: > >On Sat, Apr 23, 2011 at 05:47, Michael Schmitz > ><[email protected]> wrote: > > >> i.e. ignoring the node_present_pages return value does result in a > >> booting kernel even with the problematic commit included. > > I???m trying now (using a cross compiler, to speed up testing). > Sorry for not doing anything for a while, the ???air has left > me??? (generally and due to lack of progress with m68k as one > can only be the only fighter for ever so long).
I can understand this, but I am very impressed by all the work you have done for m68k recently! Please don't give up. > But I was just told by a member of the Debian Kernel Team on > IRC that the patches from m68k-v2.6.38 will (probably) not be > accepted, unless they go in via Linus??? tree. How are chances > of that happening? (He says they had told that years ago al- > ready.) I???ll need at least the ARAnyM/NatFeat support and some > of the bugfixes. Otherwise I fear this keeps getting obsolete > very fast. ??? As Geert wrote, almost all patches will make it into the official kernel tree, only m68k usually needs them a little sooner. Is there no m68k DD left who works on the kernel? When I was still submitting patches, there never was a problem, but I made sure that m68k patches only got applied to the m68k tree. Of course, the smaller the patches, the better, and Geert was very good with sending m68k patches upstream. In case you can not get those small patches in, I can give it a try (when I have a properly working DSL again, and more time, so I can also set up crest and kullervo...). Christian -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
