From: srinivas.kandagatla@st•com (Srinivas KANDAGATLA)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: prima2: return rather than panic on missing DT nodes
Date: Fri, 17 May 2013 07:35:31 +0100 [thread overview]
Message-ID: <5195CFB3.4090905@st.com> (raw)
In-Reply-To: <CAGsJ_4w_a=vXMeh-vbRKwD+KGqRNthx-zne=DR3iR7B-WqiUPw@mail.gmail.com>
On 17/05/13 01:30, Barry Song wrote:
> then it turns out that moving the codes to callbacks of machine is the
> right way. i will take care the init ordering issues.
Not sure if this helps but, I have done a patch for this yesterday to
fix few more issues when booting with multi_v7_defconfig then the one
pointed out by Rob .
--srini
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-ARM-prima2-remove-early-and-postcore-initcalls.patch
Type: text/x-patch
Size: 4362 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130517/156c6278/attachment.bin>
next prev parent reply other threads:[~2013-05-17 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 15:50 [PATCH] ARM: prima2: return rather than panic on missing DT nodes Rob Herring
2013-05-16 17:00 ` Srinivas KANDAGATLA
2013-05-16 20:18 ` Rob Herring
2013-05-17 0:30 ` Barry Song
2013-05-17 6:35 ` Srinivas KANDAGATLA [this message]
2013-05-17 0:31 ` Barry Song
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=5195CFB3.4090905@st.com \
--to=srinivas.kandagatla@st$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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