From: "Mark A. Greer" <mgreer@mvista.com>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Fix platform_notify functions marked __init
Date: Thu, 9 Mar 2006 10:36:17 -0700 [thread overview]
Message-ID: <20060309173617.GA29996@mag.az.mvista.com> (raw)
In-Reply-To: <1141855821.28095.18.camel@localhost.localdomain>
On Wed, Mar 08, 2006 at 10:10:20PM +0000, Adrian Cox wrote:
> While adding USB support to an MV64360 based board this week, I
> discovered that all MV64x60 boards in the kernel have platform_notify
> functions marked with __init. This causes an oops if a device is added
> after boot.
>
> The patch below removes the __init markers. I do not have all these
> boards to test on, but the change seems very unlikely to break anything
> else.
Arg... I realized this a long time ago and fixed it in my tree.
Somewhere along the line, I dropped it, I guess.
Thanks for the patch Adrian.
Mark
prev parent reply other threads:[~2006-03-09 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 22:10 [PATCH] Fix platform_notify functions marked __init Adrian Cox
2006-03-09 17:36 ` Mark A. Greer [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=20060309173617.GA29996@mag.az.mvista.com \
--to=mgreer@mvista.com \
--cc=adrian@humboldt.co.uk \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).