linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Richard Purdie" <rpurdie@rpsys.net>
To: Russell King <rmk@arm.linux.org.uk>, Andrew Morton <akpm@osdl.org>
Cc: Wolfgang Wander <wwc@rentec.com>, linux-mm@kvack.org
Subject: Re: 2.6.12-rc4-mm2
Date: Thu, 2 Jun 2005 23:28:30 +0100	[thread overview]
Message-ID: <058801c567c2$6a412de0$0f01a8c0@max> (raw)
In-Reply-To: <20050602220213.D3468@flint.arm.linux.org.uk>

Russell King:
>> > After some investigation, the guilty patch is:
>> > avoiding-mmap-fragmentation.patch
>> > (and hence) avoiding-mmap-fragmentation-tidy.patch
>
>> Wolfgang, we broke ARM.
>
> I'm not sure what happened with this, but there's someone reporting that
> -rc5-mm1 doesn't work.  Unfortunately, there's not a lot to go on:
>
> http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-May/029188.html
>
> Could be unrelated for all I know.

I found the above patch at fault, Wolfgang gave me a fix which I tested, 
confirmed working and that was going into future -mm releases last I heard. 
I've not had a chance to test -rc5 onwards myself yet due to the Nokia 
whirlwind but I doubt its the above problem.

I have heard comment that recent arm kernels on collie (sa1100) fail to boot 
for unknown reasons. The collie maintainer was looking into it - I only have 
pxa hardware to test with myself (which was working as of the last -rc4-mm 
release).

I'll update with the results of -rc5 on the pxa once I've tested it.

Cheers,

Richard 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2005-06-02 22:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050516130048.6f6947c1.akpm@osdl.org>
     [not found] ` <20050516210655.E634@flint.arm.linux.org.uk>
     [not found]   ` <030401c55a6e$34e67cb0$0f01a8c0@max>
2005-05-16 23:39     ` 2.6.12-rc4-mm2 Andrew Morton
2005-05-17  0:13       ` 2.6.12-rc4-mm2 Wolfgang Wander
2005-05-17  8:38         ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-02 21:02       ` 2.6.12-rc4-mm2 Russell King
2005-06-02 22:20         ` 2.6.12-rc4-mm2 Wolfgang Wander
2005-06-02 22:28         ` Richard Purdie [this message]
2005-06-04 14:18         ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-04 14:43         ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-05 11:39         ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-05 11:45           ` 2.6.12-rc4-mm2 Russell King
2005-06-05 18:43             ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-05 19:16               ` 2.6.12-rc4-mm2 Russell King

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='058801c567c2$6a412de0$0f01a8c0@max' \
    --to=rpurdie@rpsys.net \
    --cc=akpm@osdl.org \
    --cc=linux-mm@kvack.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=wwc@rentec.com \
    /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