From: Vincent <vincent.stehle@laposte.net>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: John David Anglin <dave.anglin@bell.net>,
Helge Deller <deller@gmx.de>,
Rolf Eike Beer <eike-kernel@sf-tec.de>,
linux-parisc@vger.kernel.org
Subject: Re: Issue booting v2.6.39 .. v3.4-rc6 on hp712/100
Date: Tue, 15 May 2012 23:01:05 +0200 [thread overview]
Message-ID: <4FB2C411.4020408@bergerie> (raw)
In-Reply-To: <1337073212.3005.12.camel@dabdike.lan>
On 05/15/2012 11:13 AM, James Bottomley wrote:
(..)
> OK, I think this is the problem. We have a depd instruction in do_alias
> which is now in the _11 fault paths.
>
> This should be the fix, if someone wants to test it before I can get
> around to building it.
Hi James,
This makes my hp712 boot now; congrats!
Works for me with v3.4-rc6 and v3.4-rc7, with the following "patches pile":
depd patch (http://www.spinics.net/lists/linux-parisc/msg04169.html)
sections patch (http://www.spinics.net/lists/linux-parisc/msg04091.html)
cache patch (http://www.spinics.net/lists/linux-parisc/msg04120.html)
v3.4-rc7
Thanks!
...I think I'll upload a git, somewhere, for convenience.
Best regards,
V.
next prev parent reply other threads:[~2012-05-15 21:01 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 21:59 Issue booting v2.6.39 .. v3.4-rc6 on hp712/100 Vincent
2012-05-09 6:53 ` Rolf Eike Beer
2012-05-09 15:55 ` John David Anglin
2012-05-09 21:14 ` Vincent
2012-05-09 21:33 ` John David Anglin
2012-05-10 2:03 ` John David Anglin
2012-05-10 6:41 ` Rolf Eike Beer
2012-05-10 16:32 ` John David Anglin
2012-05-10 19:32 ` Rolf Eike Beer
2012-05-11 21:17 ` Vincent
2012-05-13 14:32 ` Jeroen Roovers
2012-05-14 0:52 ` John David Anglin
2012-05-12 22:50 ` Helge Deller
2012-05-13 14:11 ` John David Anglin
2012-05-14 1:10 ` John David Anglin
2012-05-14 22:11 ` Helge Deller
2012-05-14 22:38 ` John David Anglin
2012-05-14 22:55 ` John David Anglin
2012-05-15 8:09 ` James Bottomley
2012-05-15 9:13 ` James Bottomley
2012-05-15 18:23 ` John David Anglin
2012-05-15 18:50 ` Helge Deller
2012-05-15 19:24 ` John David Anglin
2012-05-15 19:46 ` John David Anglin
2012-05-15 19:59 ` Helge Deller
2012-05-15 20:05 ` John David Anglin
2012-05-15 20:28 ` Helge Deller
2012-05-15 20:48 ` John David Anglin
2012-05-16 14:59 ` James Bottomley
2012-05-17 19:26 ` Helge Deller
2012-05-17 19:57 ` Rolf Eike Beer
2012-05-18 8:12 ` James Bottomley
2012-05-18 21:09 ` Helge Deller
2012-05-20 10:01 ` James Bottomley
2012-05-20 19:11 ` Helge Deller
2012-05-20 20:15 ` James Bottomley
2012-05-20 21:09 ` Helge Deller
2012-05-20 21:25 ` John David Anglin
2012-05-21 20:59 ` Helge Deller
2012-05-23 8:47 ` Peter Gantner (nephros)
2012-05-23 23:09 ` John David Anglin
2012-05-15 21:08 ` John David Anglin
2012-05-16 7:27 ` James Bottomley
2012-05-16 9:27 ` James Bottomley
2012-05-16 10:09 ` James Bottomley
2012-05-16 10:49 ` John David Anglin
2012-05-16 10:57 ` James Bottomley
2012-05-16 11:17 ` John David Anglin
2012-05-16 11:57 ` Rolf Eike Beer
2012-05-16 12:24 ` James Bottomley
2012-05-15 19:52 ` James Bottomley
2012-05-15 19:09 ` James Bottomley
2012-05-15 21:01 ` Vincent [this message]
2012-05-16 19:07 ` Helge Deller
2012-05-15 8:06 ` James Bottomley
2012-05-09 21:00 ` Vincent
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=4FB2C411.4020408@bergerie \
--to=vincent.stehle@laposte.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=eike-kernel@sf-tec.de \
--cc=linux-parisc@vger.kernel.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.