From: Sean MacLennan <smaclennan@pikatech.com>
To: "Valentine Barshak" <vbarshak@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] PowerPC 44x: use machine_device_initcall() instead ofdevice_initcall() for warp_nand
Date: Tue, 8 Apr 2008 00:21:03 -0400 [thread overview]
Message-ID: <20080408002103.1b66aeea@lappy.seanm.ca> (raw)
In-Reply-To: <20080404182437.GA18185@ru.mvista.com>
On Fri, 4 Apr 2008 22:24:37 +0400
"Valentine Barshak" <vbarshak@ru.mvista.com> wrote:
> With a multiplatform kernel, once built we always have
> warp_setup_nand_flash() called and NDFC probed, no matter what
> machine we actually run on. This potentially can cause problems (such
> as kernel crash), since NDFC is probed at a warp-predefined address.
> Using machine_device_initcall() NAND devices are registered if we run
> on a warp only.
Thanks for catching that. I have gotten *way* behind on my email and am
only reading this now.
Cheers,
Sean
prev parent reply other threads:[~2008-04-08 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 18:24 [PATCH] PowerPC 44x: use machine_device_initcall() instead of device_initcall() for warp_nand Valentine Barshak
2008-04-04 18:49 ` Grant Likely
2008-04-08 4:21 ` Sean MacLennan [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=20080408002103.1b66aeea@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=vbarshak@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).