>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). 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. ☹ bye, //mirabilos -- <ch> you introduced a merge commit │<mika> % g rebase -i HEAD^^ <mika> sorry, no idea and rebasing just fscked │<mika> Segmentation <ch> should have cloned into a clean repo │ fault (core dumped) <ch> if I rebase that now, it's really ugh │<mika:#grml> wuahhhhhh -- 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
