From: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
To: Barry Song <21cnbao@gmail.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>,
Barry Song <baohua.song@csr.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 2/2] ARM:prima2:move postcore_initcalls to init_machine.
Date: Mon, 03 Jun 2013 09:56:51 +0100 [thread overview]
Message-ID: <51AC5A53.1090700@st.com> (raw)
In-Reply-To: <CAGsJ_4yu2MT5o7hbX67KPhrejS9D1BbPcship4zxtXs3G9tE-Q@mail.gmail.com>
On 03/06/13 04:51, Barry Song wrote:
> did you see this one?
>
> [PATCH v2] arm: prima2: use of_platform_populate instead of
> of_platform_bus_probe
> http://www.spinics.net/lists/arm-kernel/msg243710.html
Yes, I think this is a nice cleanup for simplest case. But Prima
platforms do much more checking at the same init level. An attempt to
get rid of postcore and early init calls might introduce this back.
You could solve both the early and postcore initcall issues by returning
instead of panic, and let every NON Prima platforms call this function.
Or
Do it the right way and clean it up.
I will leave it up to you to decide on how you want to fix the multi_v7
kernel issue.
Thanks,
srini
next prev parent reply other threads:[~2013-06-03 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 9:43 [PATCH v1 0/2] ARM:prima2: multi_v7 kernel fixes Srinivas KANDAGATLA
2013-05-31 9:45 ` [PATCH v1 1/2] ARM:prima2: move sirfsoc_of_rstc_init to .init_early Srinivas KANDAGATLA
2013-05-31 12:24 ` Barry Song
2013-05-31 12:42 ` Srinivas KANDAGATLA
2013-05-31 12:56 ` Barry Song
2013-06-03 2:19 ` Barry Song
2013-06-03 8:47 ` Srinivas KANDAGATLA
2013-06-03 9:41 ` Barry Song
2013-05-31 9:45 ` [PATCH v1 2/2] ARM:prima2:move postcore_initcalls to init_machine Srinivas KANDAGATLA
2013-06-03 3:51 ` Barry Song
2013-06-03 8:56 ` Srinivas KANDAGATLA [this message]
2013-06-03 10:07 ` Barry Song
2013-06-03 10:46 ` Srinivas KANDAGATLA
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=51AC5A53.1090700@st.com \
--to=srinivas.kandagatla@st.com \
--cc=21cnbao@gmail.com \
--cc=arnd@arndb.de \
--cc=baohua.song@csr.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=workgroup.linux@csr.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