From: Kristian Mueller <Kristian-M@kristian-m.de>
To: Romain Goyet <r.goyet@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Problem in arch/arm/mm between 2.6.13-rc1 and 2.6.15-rc2
Date: Thu, 08 Dec 2005 09:33:30 +0100 [thread overview]
Message-ID: <1134030810.2994.30.camel@pismo> (raw)
In-Reply-To: <8028e5750512020508g68c5fe5fl@mail.gmail.com>
Hi Romain
> I managed to find out that the kernel
> crashes in paging_init, but I couldn't find out why.
> Could you give me any suggestions ? In particular, I would like to
> know what changed in arch/arm/mm between 2.6.13 and 2.6.15, since
> 2.6.13 was working like a charm.
You can see the changes made in arch/arm/mm/init.c in the git history at
http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=history;f=arch/arm/mm/init.c
Maybe you can try older versions to isolate the date of the patch...
Best Regards
Kristian
prev parent reply other threads:[~2005-12-08 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 13:08 Problem in arch/arm/mm between 2.6.13-rc1 and 2.6.15-rc2 Romain Goyet
2005-12-08 8:33 ` Kristian Mueller [this message]
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=1134030810.2994.30.camel@pismo \
--to=kristian-m@kristian-m.de \
--cc=linux-omap-open-source@linux.omap.com \
--cc=r.goyet@gmail.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