public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@googlemail.com>
To: Thorsten Glaser <tg@mirbsd.de>, linux-m68k@vger.kernel.org
Subject: Re: Fix for SLUB?
Date: Sun, 24 Apr 2011 14:06:16 +1200	[thread overview]
Message-ID: <4DB38598.5000607@gmail.com> (raw)
In-Reply-To: <20110423185725.GA16947@chumley.earth.sol>

Christian T. Steigies wrote:
>> 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.
>   
I'll second this sentiment wholeheartedly. It's been good to see a fresh 
face injecting a lot of life into the project.
>  
>   
>> 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...).
>   
At the very least, the Debian kernel maintainers ought to take a small 
patch to disable SLUB for m68k for as long as it takes to get this fix 
included via upstream and possibly backporting.

Cheers,

  Michael

  parent reply	other threads:[~2011-04-24  2:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  8:19 Fix for SLUB? (was: Fwd: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards) Geert Uytterhoeven
2011-04-23  1:31 ` Michael Schmitz
2011-04-23  2:14   ` Michael Schmitz
2011-04-23  3:47     ` Michael Schmitz
2011-04-23 13:08       ` Geert Uytterhoeven
2011-04-23 15:39         ` Fix for SLUB? Thorsten Glaser
2011-04-23 18:57           ` Christian T. Steigies
2011-04-23 21:00             ` Debian/m68k kernel (preview) Thorsten Glaser
2011-04-24  4:00               ` Ben Hutchings
2011-04-24 11:18                 ` Thorsten Glaser
2011-04-24 20:07                 ` Thorsten Glaser
2011-04-25  3:08                   ` Michael Schmitz
2011-04-24  2:06             ` Michael Schmitz [this message]
2011-04-24  8:26               ` Fix for SLUB? Geert Uytterhoeven
2011-04-23 17:09       ` Fix for SLUB? (was: Fwd: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards) Andreas Schwab
2011-04-24  2:19         ` Michael Schmitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DB38598.5000607@gmail.com \
    --to=schmitzmic@googlemail.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@mirbsd.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox