From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: Kirkwood, kernel 3.2, vmalloc region overlap, not starting up
Date: Tue, 7 Feb 2012 17:18:38 +0100 [thread overview]
Message-ID: <20120207161838.GF15165@lunn.ch> (raw)
In-Reply-To: <4F314D0C.50501@kernelconcepts.de>
> Apart from my joy - the basic reason for that change would be still
> interesting? Does this only apply to Kirwoods or my special board?
I think the conversation fizzled out without coming to a conclusion
what is wrong. Look back in the archives and see what you can find.
The problem hits kirkwood, but i don't know if it also affects other
Orion based processors. u-boot also play a role in the problem...
Andrew
next prev parent reply other threads:[~2012-02-07 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 15:29 Kirkwood, kernel 3.2, vmalloc region overlap, not starting up Andrew Lunn
2012-02-07 16:10 ` Nils Faerber
2012-02-07 16:14 ` Russell King - ARM Linux
2012-02-07 16:18 ` Andrew Lunn [this message]
2012-02-07 16:51 ` Russell King - ARM Linux
2012-02-07 17:01 ` Nils Faerber
2012-02-07 16:55 ` Johannes Stezenbach
-- strict thread matches above, loose matches on Subject: below --
2012-02-07 14:41 Nils Faerber
2012-02-13 16:17 ` Russell King - ARM Linux
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=20120207161838.GF15165@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.