From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG][arm-soc] kernel panic in boot on Openblocks with the latest kernel
Date: Fri, 01 Mar 2013 09:05:37 +0100 [thread overview]
Message-ID: <51306151.6010008@free-electrons.com> (raw)
In-Reply-To: <20130301080030.GD5688@xps8300>
On 03/01/2013 09:00 AM, Heikki Krogerus wrote:
> Hi Jason,
>
> On Thu, Feb 28, 2013 at 09:29:30AM -0500, Jason Cooper wrote:
>> If you have a moment, could you put this into a formal patch and send to
>> lakml? If I could Gregory and Masami's Tested-by's on that, I'll queue
>> it up for -rc1/2.
>
> OK, I'll prepare the patch. I thought that Gregory was going to create
> a patch for this.
If you want I still can take care of it.
>
> Br,
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-03-01 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 11:13 [BUG][arm-soc] kernel panic in boot on Openblocks with the latest kernel Masami Hiramatsu
2013-02-28 11:34 ` Heikki Krogerus
2013-02-28 11:50 ` Masami Hiramatsu
2013-02-28 14:29 ` Jason Cooper
2013-03-01 8:00 ` Heikki Krogerus
2013-03-01 8:05 ` Gregory CLEMENT [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=51306151.6010008@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox